Method and apparatus of processing digital broadcasting signal including transmission ensemble number fields in transmitter and receiver

ABSTRACT

According to one embodiment, a method of processing a digital broadcasting signal in a transmitter includes: performing RS (Reed-Solomon) encoding on signaling data containing cross layer information between a physical layer and a upper layer; interleaving the RS encoded signaling data, wherein interleaving the RS encoded signaling data includes writing the RS encoded signaling data row-by-row from left-to-right and top-to-bottom in a signaling data block, and outputting the signaling data in the signaling data block by reading column-by-column from top-to-bottom and left-to-right; and transmitting the digital broadcasting signal including the mobile service data and the interleaved signaling data during slots.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/886,284, filed on Sep. 20, 2010, now U.S. Pat. No. 8,391,314, whichclaims the benefit of U.S. Provisional Application No. 61/244,436, filedon Sep. 21, 2009, the contents of which are hereby incorporated byreference herein in their entirety.

BACKGROUND OF THE INVENTION

1. The Field of the Invention

The present invention relates to a digital broadcasting system forprocessing the digital broadcasting signal in transmitter and receiver,and more particularly, to a transmitting system and a method forprocessing and transmitting the digital broadcast signal, and areceiving system and a method for processing the digital broadcastsignal in the receiving system.

2. Description of the Related Art

The Vestigial Sideband (VSB) transmission mode, which is adopted as thestandard for digital broadcasting in North America and the Republic ofKorea, is a system using a single carrier method. Therefore, thereceiving performance of the digital broadcast receiving system may bedeteriorated in a poor channel environment. Particularly, sinceresistance to changes in channels and noise is more highly required whenusing portable and/or mobile broadcast receivers, the receivingperformance may be even more deteriorated when transmitting mobileservice data by the VSB transmission mode.

SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to a transmitting systemand a method of processing a digital broadcast signal in a transmittingsystem that substantially obviate one or more problems due tolimitations and disadvantages of the related art.

An object of the present invention is to provide a transmission systemwhich is able to transmit additional mobile service data whilesimultaneously maintaining the compatibility with a conventional systemfor transmitting a digital broadcast signal, and a method for processinga broadcast signal.

Another object of the present invention is to provide a method oftransmitting mobile services that can flexibly respond to changes in amobile broadcasting system, by processing a partial region of a datagroup so as to be compatible with the conventional mobile broadcastingsystem, or by processing the entire region of a data group so as to beused for a new mobile broadcasting system.

Another object of the present invention is to provide a transmissionsystem which generates information of additional mobile service data byextending signaling information and transmits the generated informationto a reception system, such that the transmission system and thereception end can smoothly communicate with each other, and a method forprocessing a broadcast signal.

Another object of the present invention is to provide an extendedsignaling data structure for a Scalable Full Channel Mobile Mode(SFCMM).

Another object of the present invention is to provide a method forallowing both an SFCMM receiver and a Core Mobile Mode (CMM) receiver toprocess extended signaling data.

Additional advantages, objects, and features of the invention will beset forth in part in the description which follows and in part willbecome apparent to those having ordinary skill in the art uponexamination of the following or may be learned from practice of theinvention. The objectives and other advantages of the invention may berealized and attained by the structure particularly pointed out in thewritten description and claims hereof as well as the appended drawings.

To achieve these objects and other advantages and in accordance with thepurpose of the invention, as embodied and broadly described herein, amethod of processing a digital broadcasting signal in a transmitterincludes performing RS (Reed-Solomon) encoding on signaling datacontaining cross layer information between a physical layer and a upperlayer, wherein the signaling data includes a first field indicating aprotocol version change of the signaling data, a second field indicatinga length of an extension field of a header included in the signalingdata, and at least one field indicating a number of ensembles for atleast one of a first transmission mode and a second transmission mode,and wherein the ensembles include a collection of services, each of theservices being a package of packetized streams of mobile service data,forming data groups including the signaling data and the mobile servicedata, forming mobile service data packets including the signaling dataand the mobile service data in the data groups, transmitting the digitalbroadcasting signal including the mobile service data packets duringslots, wherein the first transmission mode is a mode in which the mobileservice data are transmitted while reserving greater than 118 packetsout of 156 packets in the slot and the second transmission mode is amode in which the mobile service data are transmitted while reservingless than or equal to 118 packets out of 156 packets in the slot.

When the first field represents a protocol version change of thesignaling data, the second field represents the length of an extensionfield of a header intended for the first transmission mode.

The signaling data includes a third field indicating a number ofensembles of the first transmission mode.

The signaling data includes the header and a payload, and the payloadincludes a number of ensemble information according to the number ofensembles of the first transmission mode.

A transmitter for processing a digital broadcasting signal includes anencoder performing RS (Reed-Solomon) encoding on signaling datacontaining cross layer information between a physical layer and a upperlayer, wherein the signaling data includes a first field indicating aprotocol version change of the signaling data, a second field indicatinga length of an extension field of a header included in the signalingdata, and at least one field indicating a number of ensembles for atleast one of a first transmission mode and a second transmission mode,and wherein the ensembles include a collection of services, each of theservices being a package of packetized streams of mobile service data, agroup formatter forming data groups including the signaling data and themobile service data, a packet formatter forming mobile service datapackets including the signaling data and the mobile service data in thedata groups, a transmission unit transmitting the digital broadcastingsignal including the mobile service data packets during slots, whereinthe first transmission mode is a mode in which the mobile service dataare transmitted while reserving greater than 118 packets out of 156packets in the slot and the second transmission mode is a mode in whichthe mobile service data are transmitted while reserving less than orequal to 118 packets out of 156 packets in the slot.

A method of processing a digital broadcasting signal in a receiverincludes receiving a digital broadcasting signal including data groupsduring slots, wherein the data groups including signaling data andmobile service data, wherein the signaling data contains cross layerinformation between a physical layer and a upper layer, wherein thesignaling data includes a first field indicating a protocol versionchange of the signaling data, a second field indicating a length of anextension field of a header included in the signaling data, and at leastone field indicating a number of ensembles for at least one of a firsttransmission mode and a second transmission mode, and wherein theensembles include a collection of services, each of the services being apackage of packetized streams of mobile service data, demodulating thebroadcasting signal, decoding the signaling data from the demodulatedbroadcasting signal, wherein the first transmission mode is a mode inwhich the mobile service data are transmitted while reserving greaterthan 118 packets out of 156 packets in the slot and the secondtransmission mode is a mode in which the mobile service data aretransmitted while reserving less than or equal to 118 packets out of 156packets in the slot.

The first field represents a protocol version change of the signalingdata, the second field represents the length of an extension field of aheader intended for the first transmission mode.

The signaling data includes a third field indicating a number ofensembles of the first transmission mode.

The signaling data includes the header and a payload, and the payloadincludes a number of ensemble information according to the number ofensembles of the first transmission mode.

The receiver processes a third field indicating a number of ensembles ofthe first transmission mode included in the signaling data when thesecond field represents the length of an extension field of a headerintended for the first transmission mode.

A receiver for processing a digital broadcasting signal includes areceiving unit receiving a digital broadcasting signal including datagroups during slots, wherein the data groups including signaling dataand mobile service data, wherein the signaling data contains cross layerinformation between a physical layer and a upper layer, wherein thesignaling data includes a first field indicating a protocol versionchange of the signaling data, a second field indicating a length of anextension field of a header included in the signaling data, and at leastone field indicating a number of ensembles for at least one of a firsttransmission mode and a second transmission mode, and wherein theensembles include a collection of services, each of the services being apackage of packetized streams of mobile service data, a demodulatordemodulating the broadcasting signal, a decoder decoding the signalingdata from the demodulated broadcasting signal, wherein the firsttransmission mode is a mode in which the mobile service data aretransmitted while reserving greater than 118 packets out of 156 packetsin the slot and the second transmission mode is a mode in which themobile service data are transmitted while reserving less than or equalto 118 packets out of 156 packets in the slot.

It is to be understood that both the foregoing general description andthe following detailed description of the present invention areexemplary and explanatory and are intended to provide furtherexplanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a data frame (M/H frame) structure fortransmitting/receiving mobile service data according to one embodimentof the present invention.

FIG. 2 is a block diagram illustrating a transmission system accordingto an embodiment of the present invention.

FIG. 3 illustrates a data frame encoder according to an embodiment ofthe present invention.

FIG. 4 illustrates a payload of an RS frame being outputted from a dataframe encoder 103 according to an embodiment of the present invention.

FIG. 5 illustrate a process of one or two RS frame being divided intoseveral portions, based upon an RS frame mode value, and a process ofeach portion being assigned to a corresponding region within therespective data group.

FIG. 6 illustrates the operations of an RS-CRC encoder according to anembodiment of the present invention.

FIG. 7 illustrates the operation of the RS frame divider according to anembodiment of the present invention, when the output of the RS frameencoder corresponds to a primary RS frame or a secondary RS frame.

FIG. 8 illustrates a diagram showing a detailed structure of a blockprocessor according to an embodiment of the present invention.

FIG. 9 illustrates a diagram showing a detailed structure of a groupformatter according to an embodiment of the present invention.

FIG. 10 illustrates a structure acquired data group before the datagroup is interleaved, when the data group includes 118 of mobile servicedata packets, according to an embodiment of the present invention.

FIG. 11 illustrates a structure acquired data group after the data groupis interleaved, when the data group includes 118 mobile service datapackets, according to an embodiment of the present invention.

FIG. 12 illustrates a data group including (118+M) mobile service datapackets according to an embodiment of the present invention.

FIG. 13 illustrates a structure of a data group after being processedwith interleaving according to the embodiment of the present invention,wherein the data group includes (118+M) number of mobile service datapackets.

FIG. 14 illustrates an exemplary assignment order of data groups beingassigned to one of 5 sub-frames, wherein the 5 sub-frames configure anM/H frame.

FIG. 15 illustrates a method for transmitting a primary or secondaryensemble/RS frame through an A, B, C, D, or E region in a data groupaccording to an embodiment of the present invention.

FIG. 16 illustrates an example of transmitting 3 parades (Parade #0,Parade #1, and Parade #2) to an M/H frame.

FIG. 17 illustrates a detailed block diagram of the signaling encoderaccording to the present invention.

FIG. 18 illustrates how a block interleaver in a signaling encoderoperates to interleave FIC data according to an embodiment of thepresent invention.

FIG. 19 illustrates a syntax structure of an FIC chunk header accordingto an embodiment of the present invention.

FIG. 20 illustrates an exemplary syntax structure of an FIC chunkpayload according to an embodiment of the present invention.

FIG. 21 illustrates mapping of an FIC chunk to an FIC segment deliveryunit according to an embodiment of the present invention.

FIG. 22 illustrates an exemplary syntax structure of an FIC segmentheader according to an embodiment of the present invention.

FIG. 23 is a block diagram of a digital broadcast receiver according toan embodiment of the present invention.

FIG. 24 illustrates a block view of the signaling decoder according toan embodiment of the present invention.

FIG. 25 illustrates a method in which a CMM receiver and an SFCMMreceiver process data according to FIC header information according toan embodiment of the present invention.

FIG. 26 illustrates a method for processing a digital broadcast signalat the transmitting side according to an embodiment of the presentinvention.

FIG. 27 illustrates a method for processing a digital broadcast signalat the receiving side according to an embodiment of the presentinvention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

In addition, although the terms used in the present invention areselected from generally known and used terms, some of the termsmentioned in the description of the present invention have been selectedby the applicant at his or her discretion, the detailed meanings ofwhich are described in relevant parts of the description herein.Furthermore, it is required that the present invention is understood,not simply by the actual terms used but by the meaning of each termlying within.

For convenience of description and better understanding of the presentinvention, abbreviations and terms to be use in the present inventionare defined as follows.

Among the terms used in the description of the present invention, mainservice data correspond to data that can be received by a fixedreceiving system and may include audio/video (A/V) data. Morespecifically, the main service data may include A/V data of highdefinition (HD) or standard definition (SD) levels and may also includediverse data types required for data broadcasting. Also, the known datacorrespond to data pre-known in accordance with a pre-arranged agreementbetween the receiving system and the transmitting system.

Additionally, among the terms used in the present invention, “M/H (orMH)” corresponds to the initials of “mobile” and “handheld” andrepresents the opposite concept of a fixed-type system. Furthermore, theM/H service data may include at least one of mobile service data andhandheld service data, and will also be referred to as “mobile servicedata” for simplicity. Herein, the mobile service data not onlycorrespond to M/H service data but may also include any type of servicedata with mobile or portable characteristics. Therefore, the mobileservice data according to the present invention are not limited only tothe M/H service data.

The above-described mobile service data may correspond to data havinginformation, such as program execution files, stock information, and soon, and may also correspond to A/V data. Most particularly, the mobileservice data may correspond to A/V data having lower resolution andlower data rate as compared to the main service data. For example, if anA/V codec that is used for a conventional main service corresponds to aMPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable videocoding (SVC) having better image compression efficiency may be used asthe A/V codec for the mobile service. Furthermore, any type of data maybe transmitted as the mobile service data. For example, transportprotocol expert group (TPEG) data for broadcasting real-timetransportation information may be transmitted as the main service data.

Also, a data service using the mobile service data may include weatherforecast services, traffic information services, stock informationservices, viewer participation quiz programs, real-time polls andsurveys, interactive education broadcast programs, gaming services,services providing information on synopsis, character, background music,and filming sites of soap operas or series, services providinginformation on past match scores and player profiles and achievements,and services providing information on product information and programsclassified by service, medium, time, and theme enabling purchase ordersto be processed. Herein, the present invention is not limited only tothe services mentioned above.

Additionally, in the embodiment of the present invention, a group (alsoreferred to as an M/H group or a data group) corresponds to a collection(or group) of data packets confined within a slot (also referred to asan M/H slot).

A group division refers to a set of group regions within a slot. Herein,a group division is categorized into a Primary Group Division or aSecondary Group Division. At this point, a collection of primary groupdivisions within an M/H frame configures (or forms) a primary parade,whereas a collection of secondary group divisions configures (or forms)a secondary parade or an overlay parade.

A group type is determined by the configuration of a group divisionwithin a single group.

A parade (also referred to as an M/H parade) refers to a collection ofgroups that have the same FEC parameters. More specifically, a paraderefers to a collection of group divisions of groups having the samegroup type.

A primary parade (also referred to as a primary M/H parade) correspondsto a collection of primary group divisions, and a secondary parade (alsoreferred to as a secondary M/H parade) corresponds to a collection ofsecondary group divisions. Each of the secondary group divisions iscarried (or transported) through the same slot with its respectivelypaired primary group division. The secondary parade has the same paradeidentifier (ID) as its respective primary parade (i.e., the secondaryparade shares the same parade ID with its respective primary parade)

An overlay parade (also referred to as an overlay M/H parade)corresponds to a collection of secondary group divisions. And, in thiscase, the secondary group divisions are not paired with any of theprimary group divisions.

An RS frame corresponds to a two (2)-dimensional (2D) data frame,wherein an RS frame payload is RS-CRC encoded.

In a primary RS frame, a primary RS frame parade is RS-CRC encoded. Theprimary RS frame is transmitted (or carried) through a primary parade.

In a secondary RS frame, a secondary RS frame parade is RS-CRC encoded.The secondary RS frame is transmitted (or carried) through a secondaryparade.

In an overlay RS frame, an overlay RS frame payload is RS-CRC encoded.The overlay RS frame is transmitted (or carried) through an overlayparade.

A super RS frame corresponds to an RS frame wherein a super RS framepayload is RS-CRC encoded. The super RS frame is transported (orcarried) through two arbitrary parades.

An ensemble (also referred to as an M/H ensemble) refers to a collectionof RS frame having the same FEC codes. Herein, each RS frameencapsulates a collection of a collection of IP streams.

A primary ensemble corresponds to a collection of consecutive primary RSframes.

A secondary ensemble corresponds to a collection of consecutivesecondary RS frames.

An overlay ensemble corresponds to a collection of consecutive overlayRS frames.

A super ensemble (also referred to as a super M/H ensemble) correspondsto a collection of consecutive super RS frames.

In the embodiment of the present invention, data for mobile services maybe transmitted by using a portion of the channel capacity that was usedto transmit data for main services. Alternatively, data for mobileservice may also be transmitted by using the entire channel capacitythat was used to transmit data for main services. The data for mobileservices correspond to data required for mobile services. Accordingly,the data for mobile services may include actual mobile service data aswell as known data, signaling data, RS parity data for error-correctingmobile service data, and so on. In the description of the embodiment ofthe present invention, the data for mobile services will be referred toas mobile service data or mobile data for simplicity.

The mobile service data may be categorized as mobile service data of afirst mobile mode or Core Mobile Mode (CMM) and mobile service data of asecond mobile mode or Extended Mobile Mode (EMM) or Scalable FullChannel Mobile Mode (SFCMM).

Furthermore, when the second mobile mode is used along with the firstmobile mode, the above-described two modes may be collectively definedas the Scalable Full Channel Mobile Mode (SFCMM).

The first mobile mode is a mode in which Mobile DTV services aretransmitted while reserving at least 38 of the 156 packets in each M/HSlot for legacy A/53-compatible services. The second mobile mode is amode in which Mobile DTV services are transmitted while reserving fewerthan 38 of the 156 packets in some or all M/H Slots for legacyA/53-compatible services.

According to the definition of CMM, SFCMM, Ensemble and Parade, the CMMensemble is a Primary or Secondary Ensemble that is compatible with theCMM system. A CMM Ensemble carries a collection of CMM Services and theSFCMM ensemble is a Primary or Secondary Ensemble that carries acollection of SFCMM Services and is backwards compatible with, but notrecognizable by, a CMM receiver/decoder.

And also, the CMM Parade is an M/H Parade that is compatible with theCMM system. A CMM Parade consists of DATA Groups, where each DATA Groupdoes not include the Group Region E and carries an entire RS Framebelonging to the corresponding CMM Ensemble.

The SFCMM Parade is an M/H Parade that is backwards compatible with, butnot recognizable by, a CMM system receiver/decoder. An SFCMM Paradeconsists of DATA Groups, where each DATA Group contains the Group RegionE and carries an entire RS Frame belonging to the corresponding SFCMMEnsemble.

The CMM Service is an M/H Service that is compatible with the CMMsystem. A CMM Service is delivered through a CMM Ensemble. And the CMMService is an M/H Service that is compatible with the CMM system. A CMMService is delivered through a CMM Ensemble.

Also, according to an embodiment of the present invention, a group (alsoreferred to as an M/H group or a data group) corresponds to a collectionof M/H Encapsulated (MHE) data packets confined within a slot (alsoreferred to as an M/H slot).

A group division corresponds to a collection (or set) of group regions(also referred to as M/H group regions) within a slot. Herein, a groupdivision is categorized into a Primary Group Division or a SecondaryGroup Division.

A group region corresponds to a collection (or set) of DATA blocks orextended DATA blocks.

A group type is determined by the configuration of a group divisionwithin a single group.

Known data is pre-recognized by an agreement between a transmissionsystem and a reception system, and may be used for channel equalization,etc.

FEC is an abbreviation of a Forward Error Correction, and is a genericname of technologies wherein a reception end can spontaneously correctan error of a digital signal transmitted from the transmission end tothe reception end without retransmission of a corresponding signal bythe transmission end.

TPC is an abbreviation of a Transmission Parameter Channel. TPC iscontained in each data group, and then transmitted. The TPC providesinformation about a data frame and a data group to the reception end,and performs signaling of the provided information.

TS is an abbreviation of a Transport Stream.

RS is an abbreviation of Reed-Solomon.

CRC is an abbreviation of a Cyclic Redundancy Check.

SCCC is an abbreviation of a Serial Concatenated Convolutional Code.

PCCC is an abbreviation of a Parallel Concatenated Convolutional Code.

FIC is an abbreviation of a Fast information channel. FIC carriescross-layer information. This information primarily includes channelbinding information between ensembles and services.

Embodiments of the present invention will hereinafter be described withreference to the annexed drawings.

FIG. 1 illustrates a data frame (M/H frame) structure fortransmitting/receiving mobile service data according to one embodimentof the present invention.

In the embodiment of the present invention, the mobile service data arefirst multiplexed with main service data in data frame units and, then,modulated in a VSB mode and transmitted to the receiving system.

The term “data frame” mentioned in the embodiment of the presentinvention may be defined as the concept of a time during which mainservice data and mobile service data are transmitted. For example, onedata frame may be defined as a time consumed for transmitting 20 VSBdata frames.

At this point, one data frame consists of K1 number of sub-frames,wherein one sub-frame includes K2 number of slots. Also, each slot maybe configured of K3 number of data packets. In the embodiment of thepresent invention, K1 will be set to 5, K2 will be set to 16, and K3will be set to 156 (i.e., K1=5, K2=16, and K3=156). The values for K1,K2, and K3 presented in this embodiment either correspond to valuesaccording to a preferred embodiment or are merely exemplary. Therefore,the above-mentioned values will not limit the scope of the presentinvention.

In the example shown in FIG. 1, one data frame consists of 5 sub-frames,wherein each sub-frame includes 16 slots. In this case, the data frameaccording to the present invention includes 5 sub-frames and 80 slots.

Also, in a packet level, one slot is configured of 156 data packets(i.e., transport stream packets), and in a symbol level, one slot isconfigured of 156 data segments. Herein, the size of one slotcorresponds to one half (½) of a VSB field. More specifically, since one207-byte data packet has the same amount of payload data as payload dataof a segment, a data packet prior to being interleaved may also be usedas a data segment.

156 data packets contained in a slot may be composed of 156 main servicedata packets, may be composed of 118 mobile service data packets and 38main service data packets, or may be composed of (118+M) mobile servicedata packets and L main service data packets. In this case, the sum of Mand L may be set to 38 according to one embodiment of the presentinvention. In addition, M may be zero ‘0’ or a natural number of 38 orless.

One data group is transmitted during a single slot. In this case, thetransmitted data group may include 118 mobile service data packets or(118+M) mobile service data packets.

That is, a data group may be defined as a set of data units includingmobile service data present in one slot. In this case, the mobileservice data may be defined as pure mobile service data, or may bedefined as the concept that includes data for transmitting mobileservice data, such as signaling data, known data, etc.

FIG. 2 is a block diagram illustrating a transmission system accordingto an embodiment of the present invention.

Referring to FIG. 2, the transmission system includes a packetadjustment unit 101, a pre-processor 102, a data frame encoder 103, ablock processor 104, a signaling encoder 105, a group formatter 106, apacket formatter 107, a Packet multiplexer (Packet MUX) 108, apost-processor 109, a modified data randomizer 110, asystematic/non-systematic RS encoder 111, a data interleaver 112, anon-systematic RS encoder 113, a parity replacer 114, a modified trellisencoder 115, a synchronization multiplexer (Sync MUX) 116, a pilotinserter 117, a VSB modulator 118, and a Radio Frequency (RF)up-converter 119. In addition, the transmission system of FIG. 2 mayfurther include a pre-equalizer filter 120.

When a mobile service data packet and a main service data packet aremultiplexed, there may occur a displacement between a service streampacket including a mobile service stream and another service streampacket including no mobile service stream. In order to compensate forthe displacement, the packet adjustment unit 101 may be used.

The pre-processor 102 configures mobile service data in a form of amobile service structure for transmitting the mobile service data. Inaddition, the pre-processor 102 performs additional FEC coding of mobileservice data. Also, the pre-processor 102 inserts known data. That is,the pre-processor 102 increases the stability of transmission andreception of mobile service data under a mobile environment.

Also, the pre-processor 102 performs an additional encoding process onthe mobile service data of the first mobile mode extracted from themobile service data packet of the first mobile mode and/or on the mobileservice data of the second mobile mode extracted from the mobile servicedata packet of the second mobile mode, and the pre-processor 102 alsoperforms a group forming process enabling data to be positioned in aspecific position depending upon the purpose of the data that are to betransmitted to the transmission frame. Such processes are performed toenable the mobile service data to respond more swiftly and withrobustness against noise and change in channels.

The pre-processor 102 may include a data frame encoder 103, a blockprocessor 103, a block processor 104, a signaling encoder 105, a groupformatter 106, a packet formatter 107, and a packet multiplexer (packetMUX) 108. In other words, the above-mentioned constituent components maybe contained in the pre-processor 102, and may be configured separatelyfrom the pre-processor 102.

The data frame encoder 103 randomizes mobile service data of the firstmobile mode or second mobile mode, and performs RS encoding and CRCencoding of the mobile service data to build RS frame.

The mobile service data included in the RS frame may correspond tomobile service data of the first mobile mode, or may correspond tomobile service data of the second mobile mode. Furthermore, the RS framemay include both the mobile service data of the first mobile mode andthe mobile service data of the second mobile mode.

Herein, the mobile service data may be broadly divided into two types ofmobile modes. One of the mobile modes is referred to as a first mobilemode or a Core Mobile Mode (CMM), and the other mobile mode is referredto as a second mobile mode or a Scalable Full Channel Mobile Mode(SFCMM). Furthermore, the first mobile mode and the second mobile modemay be collectively referred to as the Scalable Full Channel Mobile Mode(SFCMM).

More specifically, SFCMM is a mode in which Mobile DTV services aretransmitted while reserving fewer than 38 of the 156 packets in some orall M/H Slots for legacy A/53-compatible services. Also SFCMM can besaid as a mode in which the mobile service data are transmitted whilereserving greater than 118 packets out of 156 packets in the slot. AndCMM is a mode in which Mobile DTV services are transmitted whilereserving at least 38 of the 156 packets in each M/H Slot for legacyA/53-compatible services. Also CMM can be said as a mode in which themobile service data are transmitted while reserving less than or equalto 118 packets out of 156 packets in the slot

The first mobile mode corresponds to a mode that is compatible with theconventional mobile broadcasting system. And, the second mobile mode maybe either compatible or non-compatible with the conventional mobileservice data. However, the second mobile mode corresponds to a mode thattransmits data that cannot be recognized (or acknowledged) by theconventional mobile broadcasting system.

Only mobile service data of the first mobile mode may be allocated toone group, or only mobile service data of the second mobile mode may beallocated to the one group. Alternatively, both the mobile service dataof the first mobile mode and the mobile service data of the secondmobile mode may both be allocated to one group.

Although the data of the RS frame being outputted include raw (i.e.,non-processed) mobile service data, CRC data, stuffing data, and so on,in a broader definition, such data all correspond to data for mobileservices. Therefore, the data of each frame will hereinafter bedescribed under the assumption that the data all correspond to mobileservice data.

The block processor 104 converts an RS frame portion into an SCCC block.The block processor 104 converts a mobile service data byte contained inthe SCCC block into bit-based mobile service data. The block processor104 performs convolution encoding of ½, ⅓, or ¼ rate on the bit-basedmobile service data. In this case, the ½ rate means an encoding processin which two bits are output in response to an input of one bit, the ⅓rate means an encoding process in which three bits are output inresponse to an input of two bits, and the ¼ rate means an encodingprocess in which four bits are output in response to an input of fourbits. Output bits are contained in a symbol. The block processor 104performs interleaving of the convolution-encoded output symbol. Theblock processor 104 converts an interleaved symbol into byte-based data,and converts an SCCC block into a data block. A detailed description ofthe data block will hereinafter be described in detail.

The signaling encoder 105 generates signaling information for signalingat a reception end, performs FEC encoding and PCCC encoding of thegenerated signaling information, and inserts the signaling informationinto some regions of the data group. For example, examples of thesignaling information may be a transmission parameter channel (TPC)data, fast information channel (FIC) data, and the like.

The group formatter 106 forms a data group using the output data of theblock processor 104. The group formatter 106 maps FEC-encoded mobileservice data to an interleaved form of a data group format. At thistime, the above-mentioned mapping is characterized in that FEC-encodedmobile service data is inserted into either a data block of acorresponding group or a group region according to a coding rate of eachFEC-encoded mobile service data received from the block processor 104.In addition, the group formatter 106 inserts signaling data, a data byteused for initializing the trellis encoder, and a known data sequence.Further, the group formatter 106 inserts main service data, and aplace-holder for an MPEG-2 header and a non-systematic RS parity. Thegroup formatter 106 may insert dummy data to generate a data group of adesired format. After inserting various data, the group formatter 106performs deinterleaving of data of the interleaved data group. Afterperforming the deinterleaving operation, the data group returns to anoriginal group formed before the interleaving operation.

The packet formatter 107 converts output data of the group formatter 106into a Transport Stream (TS) packet. In this case, the TS packet is amobile service data packet. In addition, the output of the packetformatter 107 according to an embodiment of the present invention ischaracterized in that it includes (118+M) mobile service data packets ina single data group. In this case, M is 38 or less.

The packet multiplexer (Packet MUX) 108 multiplexes a packet includingmobile service data processed by the pre-processor 102 and a packetincluding main service data output from the packet adjustment unit 101.In this case, the multiplexed packet may include (118+M) mobile servicedata packets and L main service data packets. For example, according toan embodiment of the present invention, M is any one of integers from 0to 38, and the sum of M and L is set to 38. In other words, although thepacket multiplexer (packet MUX) 108 may multiplex the mobile servicedata packet and the main service data packet, in the case where thenumber of input main service data packets is set to ‘0’ (i.e., L=0),only the mobile service data packet is processed by the packetmultiplexer (packet MUX) 108, such that the packet multiplexer (packetMUX) 108 outputs the processed mobile service data packet only.

The post-processor 109 processes mobile service data in such a mannerthat the mobile service data generated by the present invention can bebackward compatible with a conventional broadcast system. In accordancewith one embodiment of the present invention, the post-processor 109 mayinclude a modified data randomizer 110, a systematic/non-systematic RSencoder 111, a data interleaver 112, a non-systematic RS encoder 113, aparity replacer 114 and a modified trellis encoder 115. In other words,each of the above-mentioned constituent components may be locatedoutside of the post-processor 109 according to the intention of adesigner as necessary.

The modified data randomizer 110 does not perform randomizing of amobile service TS packet, and bypasses a mobile service TS packet. Themodified data randomizer 110 performs randomizing of the main servicedata TS packet. Therefore, according to one embodiment of the presentinvention, the randomizing operation is not performed when a data groupgenerated by the pre-processor 102 has no main service data.

In the case where input data is a main service data packet, thesystematic/non-systematic RS encoder 111 performs systematic RS encodingof the main service data packet acting as the input data, such that itgenerates RS FEC data. In the case where input data is a mobile servicedata packet, the systematic/non-systematic RS encoder 111 performsnon-systematic RS encoding, such that it generates RS FEC data. Inaccordance with one embodiment of the present invention, thesystematic/non-systematic RS encoder 111 generates RS FEC data havingthe size of 20 bytes during the systematic/non-systematic RS encodingprocess. The RS FEC data generated in the systematic RS encoding processis added to the end of a packet having the size of 187 bytes. RS FECdata generated in the non-systematic RS encoding process is insertedinto the position of an RS parity byte predetermined in each mobileservice data packet. Therefore, according to one embodiment of thepresent invention, in the case where the data group generated by thepre-processor has no main service data, the systematic RS encoder 111for main service data performs no RS encoding. In this case, thenon-systematic RS encoder 111 does not generate a non-systematic RSparity for backward compatibility.

The data interleaver 112 performs byte-based interleaving of data thatincludes main service data and mobile service data.

In the case where it is necessary to initialize the modified trellisencoder 115, the non-systematic RS encoder 113 receives an internalmemory value of the modified trellis encoder 115 as an input, andreceives mobile service data from the data interleaver 112 as an input,such that it changes initialization data of mobile service data to amemory value. The non-systematic RS encoder 113 performs non-systematicRS encoding of the changed mobile service data, and outputs thegenerated RS parity to the parity replacer 114.

In the case where it is necessary to initialize the modified trellisencoder 115, the parity replacer 114 receives mobile service data outputfrom the data interleaver 112, and replaces an RS parity of the mobileservice data with an RS parity generated from the non-systematic RSencoder 113.

In the case where the data group generated in the pre-processor does notinclude main service data at all, the data group need not have an RSparity for backward compatibility. Accordingly, in accordance with oneembodiment of the present invention, the non-systematic RS encoder 113and the parity replacer 114 do not perform each of the above-mentionedoperations, and bypass corresponding data.

The modified trellis encoder 115 performs trellis encoding of outputdata of the data interleaver 112. In this case, in order to allow dataformed after the trellis encoding to have known data pre-engaged betweena transmission end and a reception end, a memory contained in themodified trellis encoder 115 should be initialized before the beginningof the trellis encoding. The above-mentioned initialization operationbegins by trellis initialization data belonging to a data group.

The synchronization multiplexer (Sync MUX) 116 inserts a fieldsynchronization signal and a segment synchronization signal into outputdata of the modified trellis encoder 115, and multiplexes the resultantdata.

The pilot inserter 117 receives the multiplexed data from thesynchronization multiplexer (Sync MUX) 116, and inserts a pilot signal,that is used as a carrier phase synchronization signal for demodulatinga channel signal at a reception end, into the multiplexed data.

The VSB modulator 118 performs VSB modulation so as to transmit data.

The transmission unit 119 performs frequency up-conversion of themodulated signal, and transmits the resultant signal.

In the present invention, the transmitting system provides backwardcompatibility in the main service data so as to be received by theconventional receiving system. Herein, the main service data and themobile service data are multiplexed to the same physical channel andthen transmitted.

Furthermore, the transmitting system according to the present inventionperforms additional encoding on the mobile service data and inserts thedata already known by the receiving system and transmitting system(e.g., known data), thereby transmitting the processed data.

Therefore, when using the transmitting system according to the presentinvention, the receiving system may receive the mobile service dataduring a mobile state and may also receive the mobile service data withstability despite various distortion and noise occurring within thechannel.

FIG. 3 illustrates a data frame encoder according to an embodiment ofthe present invention.

(a) of FIG. 3 corresponds to an example of a data frame encoder. Thedata frame encoder receives a plurality of ensembles, and an inputdemultiplexer outputs the received ensembles by distributing thereceived ensembles to each RS frame encoder. The output of each RS frameencoder passes through an output multiplexer, so as to become the outputof the data frame encoder. According to the embodiment of the presentinvention, one data frame encoder includes a number of RS frame encoderscorresponding to the number of the received ensembles.

(b) of FIG. 3 corresponds to an example of an RS frame encoder. The RSframe encoder may include a data randomizer 3010, an RS-CRC encoder3020, and an RS Frame divider 3030.

The data randomizer 3010 randomizes data. The data randomizer 3010within the RS frame encoder randomizes an (N×187)-byte RS frame payloadincluded in the received ensemble. Thereafter, the randomized result isoutputted to the RS-CRC encoder.

The RS-CRC encoder 3020 performs forward error correction (FEC) encodingon the mobile service data, thereby building (or creating) an RS frame.At this point, the built (or created) RS frame may correspond to aprimary RS frame or a combination of a primary RS frame and a secondaryRS frame.

The RS frame divider 3030 divides the RS frame into a plurality of dataportions. Herein, according to the embodiment of the present invention,one data portion forms one data group.

A CMM primary ensemble, a CMM secondary ensemble, an EMM primaryensemble, an EMM secondary ensemble, and a super ensemble may beinputted as the input of the RS frame encoder. When a primary ensembleis inputted, primary RS frame portions are outputted from the RS framedivider. And, when a secondary ensemble is inputted, secondary RS frameportions are outputted from the RS frame divider.

FIG. 4 illustrates a payload of an RS frame being outputted from a dataframe encoder 103 according to an embodiment of the present invention.

Payloads of the RS frame are gathered (or collected) to form anensemble. Herein, an ensemble corresponds to a collection of serviceshaving the same quality of service (QoS).

A data frame encoder 103 includes at least one or more RS frameencoders. Herein, one RS frame encoder receives one RS frame payload andencodes the received RS frame payload, thereby outputting the encoded RSframe payload.

According to the embodiment of the present invention, the RS framepayload has the size of (N×187) bytes. Herein, N represents the lengthof a row (i.e., the number of columns), and 187 indicates the length ofa column the number of rows).

According to the embodiment of the present invention, each rowconfigured of N bytes will be referred to as a mobile service datapacket for simplicity. The mobile service data packet may include a2-byte header and an (N−2)-byte mobile service payload. Herein, theassignment of 2 bytes to the header region is merely exemplary.Accordingly, the assignment of the data bytes may be varied and modifiedby the system designer. Therefore, the present invention will not belimited only to the examples given in the description of the presentinvention.

According to the embodiment of the present invention, each rowconfigured of N bytes will be referred to as a mobile service datapacket for simplicity. The mobile service data packet may include a2-byte header and an (N−2)-byte mobile service payload. Herein, theassignment of 2 bytes to the header region is merely exemplary.Accordingly, the assignment of the data bytes may be varied and modifiedby the system designer. Therefore, the present invention will not belimited only to the examples given in the description of the presentinvention.

One RS frame payload is created by gathering (or collecting) tableinformation and/or IP datagrams having the size of (N−2)×187 bytes fromone ensemble. Also, one RS frame payload may include table informationand IP datagrams corresponding to at least one or more mobile services.For example, IP datagrams and table information for two different typesof mobile services, such as news (e.g., IP datagram for mobile service1) and stock information (e.g., IP datagram for mobile service 2), maybe included in one RS frame payload.

More specifically, table information of a section structure or IPdatagrams of mobile service data may be assigned to a mobile payloadwithin a mobile service data packet included in the RS frame payload.Alternatively, IP datagrams of table information or IP datagrams ofmobile service data may be assigned to a mobile payload within a mobileservice data packet included in the RS frame payload.

In case the size of a mobile service data packet does not reach the sizeof N bytes, even when including a mobile header, stuffing data bytes maybe assigned to the remaining payload portion of the corresponding mobileservice data packet. For example, after assigning program tableinformation to a mobile service data packet, if the length of the mobileservice data packet including the header is (N−20) bytes, stuffing databytes may be assigned to the remaining 20-byte portion of thecorresponding mobile service data packet.

FIG. 5 illustrate a process of one or two RS frame being divided intoseveral portions, based upon an RS frame mode value, and a process ofeach portion being assigned to a corresponding region within therespective data group.

According to an embodiment of the present invention, the data assignmentwithin the data group is performed by the group formatter.

More specifically, (a) of FIG. 5 shows an example of the RS frame modevalue being equal to ‘00’. Herein, only the primary encoder operates,thereby forming one RS frame for one parade. Then, the RS frame isdivided into several portions, and the data of each portion are assignedto regions A/B/C/D/E within the respective data group.

(b) of FIG. 5 shows an example of the RS frame mode value being equal to‘01’. Herein, both the primary encoder and the secondary encoderoperate, thereby forming two RS frames for one parade, i.e., one primaryRS frame and one secondary RS frame. Then, the primary RS frame isdivided into several portions, and the secondary RS frame is dividedinto several portions. At this point, the data of each portion of theprimary RS frame are assigned to regions A/B within the respective datagroup. And, the data of each portion of the secondary RS frame areassigned to regions CAVE within the respective data group.

FIG. 6 illustrates the operations of an RS-CRC encoder according to anembodiment of the present invention.

(a) of FIG. 6 illustrates an example of an RS frame being generated fromthe RS-CRC encoder according to the present invention.

When the RS frame payload is formed, as shown in (a) of FIG. 6, theRS-CRC encoder performs a (Nc,Kc)-RS encoding process on each column, soas to generate Nc-Kc(=P) number of parity bytes. Then, the RS-CRCencoder adds the newly generated P number of parity bytes after the verylast byte of the corresponding column, thereby creating a column of(187+P) bytes. Herein, as shown in (a) of FIG. 6, Kc is equal to 187(i.e., Kc=187), and Nc is equal to 187+P (i.e., Nc=187+P). Herein, thevalue of P may vary depending upon the RS code mode. Table a below showsan example of an RS code mode, as one of the RS encoding information.

TABLE 1 RS code mode RS code Number of parity bytes (P) 00 (211, 187) 2401 (223, 187) 36 10 (235, 187) 48 11 Reserved Reserved

Table 1 shows an example of 2 bits being assigned in order to indicatethe RS code mode. The RS code mode represents the number of parity bytescorresponding to the RS frame payload.

For example, when the RS code mode value is equal to ‘10’,(235,187)-RS-encoding is performed on the RS frame payload of FIG. 48(a), so as to generate 48 parity data bytes. Thereafter, the 48 paritybytes are added after the last data byte of the corresponding column,thereby creating a column of 235 data bytes.

When the RS frame mode value is equal to ‘00’ in Table 1 (i.e., when theRS frame mode indicates a single RS frame), only the RS code mode of thecorresponding RS frame is indicated. However, when the RS frame modevalue is equal to ‘01’ in Table 1 (i.e., when the RS frame modeindicates multiple RS frames), the RS code mode corresponding to aprimary RS frame and a secondary RS frame. More specifically, it ispreferable that the RS code mode is independently applied to the primaryRS frame and the secondary RS frame.

When such RS encoding process is performed on all N number of columns, asize of N(row)×(187+P)(column) bytes may be generated, as shown in (b)of FIG. 6.

Each row of the RS frame payload is configured of N bytes. However,depending upon channel conditions between the transmitting system andthe receiving system, error may be included in the RS frame payload.When errors occur as described above, CRC data (or CRC code or CRCchecksum) may be used on each row unit in order to verify whether errorexists in each row unit.

The RS-CRC encoder may perform CRC encoding on the mobile service databeing RS encoded so as to create (or generate) the CRC data. The CRCdata being generated by CRC encoding may be used to indicate whether themobile service data have been damaged while being transmitted throughthe channel.

The present invention may also use different error detection encodingmethods other than the CRC encoding method. Alternatively, the presentinvention may use the error correction encoding method to enhance theoverall error correction ability of the receiving system.

(c) of FIG. 6 illustrates an example of using a 2-byte (i.e., 16-bit)CRC checksum as the CRC data. Herein, a 2-byte CRC checksum is generatedfor N number of bytes of each row, thereby adding the 2-byte CRCchecksum at the end of the N number of bytes. Thus, each row is expandedto (N+2) number of bytes. Equation 1 below corresponds to an exemplaryequation for generating a 2-byte CRC checksum for each row beingconfigured of N number of bytes.g(x)=x ¹⁶ +x ¹² +x ⁵+1  [Equation 1]

The process of adding a 2-byte checksum in each row is only exemplary.Therefore, the present invention is not limited only to the exampleproposed in the description set forth herein. As described above, whenthe process of RS encoding and CRC encoding are completed, the(N×187)-byte RS frame payload is converted into a (N+2)×(187+P)-byte RSframe.

The RS frame having the size of (N+2)×(187+P) bytes, which is created bythe RS-CRC encoder, is outputted to the RS frame divider.

When an RS frame payload created from a primary ensemble is inputted tothe RS frame encoder, the RS-CRC encoder generates (or creates) aprimary RS frame. Thereafter, the generated primary RS frame passesthrough the RS frame divider, so as to be transmitted through theprimary parade.

When an RS frame payload created from a secondary ensemble is inputtedto the RS frame encoder, the RS-CRC encoder generates (or creates) asecondary RS frame. Thereafter, the generated secondary RS frame passesthrough the RS frame divider, so as to be transmitted through thesecondary parade.

The RS frame divider receives the RS frame having the size of(N+2)×(187+P) bytes, which is outputted from the RS-CRC encoder.Thereafter, the RS frame divider divides the received RS frame into aplurality of portions, thereby outputting the divided portions.

FIG. 7 illustrates the operation of the RS frame divider according to anembodiment of the present invention, when the output of the RS frameencoder corresponds to a primary RS frame or a secondary RS frame.

At this point, the number of portions divided and created from one RSframe is equal to 5×NOG. Herein, 5 corresponds to the number of subframes existing in one M/H frame, and NOG corresponds to the number ofgroup having a parade assigned to one subframe.

Herein, one portion includes data of PL bytes.

At this point, one portion is assigned to one group division, therebybeing transmitted.

When dividing an RS frame having the size of (N+2)×(187+P) bytes into(5×NOG) number of portions, wherein each portion includes PL bytes, oneportion may have a byte size smaller than PL bytes. In this case, thelast portion may include RS frame data having the size of (PL-S) bytesand may also include additional data byes of S bytes, wherein S has arandom value.

FIG. 8 illustrates a diagram showing a detailed structure of a blockprocessor according to an embodiment of the present invention.

The block processor includes an SCCC block converter 4010, a byte to bitconverter 4020, a convolutional encoder 4030, a symbol interleaver 4040,a symbol to byte converter 4050, and a data block converter 4060.

The SCCC block converter 4010 divides a primary RS frame portionoutputted from the data frame encoder into a plurality of SCCC blocks,or the SCCC block converter 4010 divides both a primary RS frame portionand a secondary RS frame portion outputted from the data frame encoderinto a plurality of SCCC blocks. The number of SCCC blocks that aredivided from the RS frame portion(s) outputted from the data frameencoder may be known by SCCC_block_mode information, which is includedin the TPC.

The byte-to-bit converter 4020 shall convert parallel bytes to serialbits for the purpose of bit-wise operation in the convolutional encode.

The convolutional encoder 4030 performs outer convolutional coding forthe SCCC. The coding rate of the convolutional encoder can be one of 1/2rate, 1/3 rate and 1/4 rate.

The symbol interleaver 4040 scrambles the output symbols from theconvolutional encoder. The symbol interleaver is a type of Blockinterleaver

The symbol-to-byte converter converts the interleaved symbols intobytes. The MSB of the output byte shall be the MSB in the first inputsymbol.

The data block converter 4060 maps the SCCC blocks to data blocks ordata blocks and extended data blocks.

More specifically, the block processor forms (or configures) an SCCCblock after receiving portions of the RS frame from the DATA frameencoder. Thereafter, the block processor outputs the SCCC block in adata block format. At this point, an extended data block is alsoincluded in the outputted data block.

According to the embodiment of the present invention, the convolutionalencoder encodes the mobile service data of the first mobile mode and themobile service data of the second mobile mode at a coding rate of 1/2 ,a coding rate of 1/4 , or a coding rate of 1/3.

FIG. 9 illustrates a diagram showing a detailed structure of a groupformatter according to an embodiment of the present invention.

The group formatter may include a group format organizer 9010, and adata deinterleaver 9020. The group format organizer 9010 inserts mobileservice data, signaling data and respective place holders in thecorresponding regions within the data group. The signaling data includesTPC (Transmission Parameter Channel) data which includes transmissionparameters required for baseband processing in a receiver and FIC (FastInformation Channel) data containing cross layer information between aphysical layer and an upper layer. And, the data deinterleaver 9020deinterleaves the inserted data and respective place holders as aninverse process of the data interleaver.

FIG. 10 illustrates a structure acquired data group before the datagroup is interleaved, when the data group includes 118 of mobile servicedata packets, according to an embodiment of the present invention.

Referring to FIG. 10, the data group includes 118 TS packets thatinclude at least one of FEC-encoded mobile service data, MPEG header,trellis initialization data, known data, signaling data, RS parity dataand dummy data. For convenience of description and better understandingof the present invention, a TS packet contained in the data group isdefined as a mobile service data packet according to the presentinvention.

The data group shown in FIG. 10 includes 118 mobile service datapackets, such that it can be recognized that the slot via which theabove-mentioned data group is transmitted is used for transmitting 38main service data packets.

FIG. 11 illustrates a structure acquired data group after the data groupis interleaved, when the data group includes 118 mobile service datapackets, according to an embodiment of the present invention.

Referring to FIG. 11, the data group including 118 mobile service datapackets is interleaved such that a data group including 170 segments isformed.

In this case, the above-mentioned example in which 118 mobile servicedata packets are distributed to 170 segments has been disclosed only forillustrative purposes and better understanding of the present invention.The number of data segments formed after the data group is interleavedmay be changed to another according to the degree of interleaving.

FIG. 11 shows an example of dividing a data group prior to beingdata-interleaved into 10 DATA blocks (i.e., DATA block 1 (B1) to DATAblock 10 (B10)). In other word, DATA Block can be defined as atransmission block containing mobile service data or main and mobileservice data in segment level. In this example, each DATA block has thelength of 16 segments. Referring to FIG. 11, only the RS parity data areallocated to a portion of 5 segments before the DATA block 1 (B1) and 5segments behind the DATA block 10 (B10). The RS parity data are excludedin regions A to D of the data group.

More specifically, when it is assumed that one data group is dividedinto regions A, B, C, and D, each DATA block may be included in any oneof region A to region D depending upon the characteristic of each DATAblock within the data group. At this point, according to an embodimentof the present invention, each DATA block may be included in any one ofregion A to region D based upon an interference level of main servicedata.

Herein, the data group is divided into a plurality of regions to be usedfor different purposes. More specifically, a region of the main servicedata having no interference or a very low interference level may beconsidered to have a more resistant (or stronger) receiving performanceas compared to regions having higher interference levels. Additionally,when using a system inserting and transmitting known data in the datagroup, wherein the known data are known based upon an agreement betweenthe transmitting system and the receiving system, and when consecutivelylong known data are to be periodically inserted in the mobile servicedata, the known data having a predetermined length may be periodicallyinserted in the region having no interference from the main service data(i.e., a region wherein the main service data are not mixed). However,due to interference from the main service data, it is difficult toperiodically insert known data and also to insert consecutively longknown data to a region having interference from the main service data.

Referring to FIG. 11, DATA block 4 (B4) to DATA block 7 (B7) correspondto regions without interference of the main service data. DATA block 4(B4) to DATA block 7 (B7) within the data group shown in FIG. 11correspond to a region where no interference from the main service dataoccurs. In this example, a long known data sequence is inserted at boththe beginning and end of each DATA block. In the description of thepresent invention, the region including DATA block 4 (B4) to DATA block7 (B7) will be referred to as “region A (=B4+B5+B6+B7)”. As describedabove, when the data group includes region A having a long known datasequence inserted at both the beginning and end of each DATA block, thereceiving system is capable of performing equalization by using thechannel information that can be obtained from the known data. Therefore,the strongest equalizing performance may be yielded (or obtained) fromone of region A to region D.

In the example of the data group shown in FIG. 11, DATA block 3 (B3) andDATA block 8 (B8) correspond to a region having little interference fromthe main service data. Herein, a long known data sequence is inserted inonly one side of each DATA block B3 and B8. More specifically, due tothe interference from the main service data, a long known data sequenceis inserted at the end of DATA block 3 (B3), and another long known datasequence is inserted at the beginning of DATA block 8 (B8). In thepresent invention, the region including DATA block 3 (B3) and DATA block8 (B8) will be referred to as “region B(=B3+B8)”. As described above,when the data group includes region B having a long known data sequenceinserted at only one side (beginning or end) of each DATA block, thereceiving system is capable of performing equalization by using thechannel information that can be obtained from the known data. Therefore,a stronger equalizing performance as compared to region C/D may beyielded (or obtained).

Referring to FIG. 11, DATA block 2 (B2) and DATA block 9 (B9) correspondto a region having more interference from the main service data ascompared to region B. A long known data sequence cannot be inserted inany side of DATA block 2 (B2) and DATA block 9 (B9). Herein, the regionincluding DATA block 2 (B2) and DATA block 9 (B9) will be referred to as“region C(=B2+B9)”.

Finally, in the example shown in FIG. 11, DATA block 1 (B1) and DATAblock 10 (B10) correspond to a region having more interference from themain service data as compared to region C. Similarly, a long known datasequence cannot be inserted in any side of DATA block 1 (B1) and DATAblock 10 (B10).

Referring to FIG. 11, it can be readily recognized that the regions Aand B of the data group includes signaling data used for signaling at areception end.

FIG. 12 illustrates a data group including (118+M) mobile service datapackets according to an embodiment of the present invention.

Referring to FIG. 12, the data group includes A, B, C, D and E regions.The data group is contained in a slot including 156 packets. That is, apredetermined number of packets contained in one slot form the datagroup, and such packets include mobile service data.

After 118 mobile service data packets fixed in the data group areinterleaved, the data group is divided into A, B, C and D regions.

Meanwhile, a variable number (M) of mobile service data packets capableof being contained in the data group are contained in an additionalregion E. In the case where the data group in one slot is composed of118 mobile service data packets, the E region can be defined as aspecific region acquired when mobile service data packets are added tothe region composed of only main service data packets. In other words,the E region may include a scalable number of mobile service datapackets in one slot.

The mapping format of the mobile service data packets in the E regionmay be changed according to the intention of a designer. In other words,according to one embodiment of the present invention, when the number ofmobile service data packets is 38 or less (i.e., M<=38) as shown in FIG.12, a specific packet region in one slot remains empty in such a mannerthat the empty specific packet region can be used as a main service datapacket region, and therefore mobile service data packets can be mappedto the remaining parts. According to another embodiment of the presentinvention, mobile service data packets can be mapped to the data groupin such a manner that M scalable mobile service data packets containedin the E region are spaced apart from one another at intervals of apredetermined distance.

Also, the mobile service data being allocated to one group may bebroadly divided into two types of mobile modes.

Herein, one of the mobile modes is referred to as a first mobile mode ora Core Mobile Mode (CMM), and the other mobile mode is referred to as asecond mobile mode or an Extended Mobile Mode (EMM) or a Scalable FullChannel Mobile Mode (SFCMM). Furthermore, the first mobile mode and thesecond mobile mode may be collectively referred to as the Scalable FullChannel Mobile Mode (SFCMM). At this point, the mobile service data ofthe first mobile mode and the mobile service data of the second mobilemode may be encoded at a coding rate of 1/2, 1/3 , or 1/4.

The first mobile mode corresponds to a mode that is compatible with theconventional mobile broadcasting system. And, the second mobile mode maybe either compatible or non-compatible with the conventional mobileservice data. However, the second mobile mode corresponds to a mode thattransmits data that cannot be recognized (or acknowledged) by theconventional mobile broadcasting system.

Only mobile service data of the first mobile mode may be allocated toone group, or only mobile service data of the second mobile mode may beallocated to the one group. Alternatively, both the mobile service dataof the first mobile mode and the mobile service data of the secondmobile mode may both be allocated to one group.

FIG. 13 illustrates a structure of a data group after being processedwith interleaving according to the embodiment of the present invention,wherein the data group includes (118+M) number of mobile service datapackets.

A data group structure shown in FIG. 13 is transmitted to the receivingsystem. More specifically, one data packet is data-interleaved anddispersed (or distributed) to a plurality of segments, thereby beingtransmitted to the receiving system. FIG. 13 shows an example of asingle group distributed to 208 data segments. At this point, since onedata packet of 207 bytes has the same data size of one data segment, apacket prior to being data-interleaved may be used as the concept of apacket.

(a) to (c) of FIG. 13 broadly illustrate the structure of a group in asegment domain according to an embodiment of the present invention. Morespecifically, FIG. 13 illustrates the structure of a group after beingprocessed with data interleaving. In other words, one data packet isdata interleaved, and the data-interleaved packet is distributed to aplurality of data segments, thereby being transmitted to the receivingsystem. (a) of FIG. 13 shows an example of regions A, B, C, and D beingdistributed to 170 data segments after being processed with datainterleaving. (b) of FIG. 13 shows an example of region E beingdistributed to 90 data segments, when a region E exists within thegroup, after being processed with data interleaving. And, (c) of FIG. 13shows an example of one group including regions A, B, C, D, and E beingdistributed to 208 data segments after being processed with datainterleaving. At this point, since a data packet of 207 bytes has thesame data size as one data segment, a packet prior to beingdata-interleaved may be used as the concept of a packet.

(a) of FIG. 13 illustrates an example of dividing a region correspondingto the first 118 data packets among a total of 156 data packets within adata group after being processed with data-interleaving into 12 DATAblocks (MH blocks B0 to B11). Also, according to the embodiment of thepresent invention, each of the DATA blocks B1 to B10 has the length of16 segments, and DATA block B0 and DATA block B11 each has the length of5 segments.

Herein, when it is assumed that one group includes at least regions A,B, C, and D, depending upon the characteristics of each DATA blockwithin the group, each DATA block may be included in any one of region Ato region D. At this point, according to the embodiment of the presentinvention, and depending upon the level (or degree) of interference ofthe main service data, each DATA block is included in any one regionamong region A to region D.

Herein, the group is divided into multiple regions so that each regioncan be used for a different purpose. More specifically, this is becausea region having no interference from the main service data may yield amore robust data receiving performance (or capability) that a regionhaving interference from the main service data. Also, when a systemtransmitting data by inserting known data, which are pre-known inaccordance with an agreement between the receiving system and thetransmitting system, in a group is applied, known data having apredetermined length may be periodically inserted in a region wherethere is no interference from the main service data (i.e., in a regionthat is not mixed with the main service data). However, in a regionhaving interference from the main service data, due to the interferenceof the main service data, it is difficult to periodically insert knowndata, and it is also difficult to insert consecutively long known data.

DATA block B4 to DATA block B7 within the group shown in (a) of FIG. 13collectively correspond to a region having no interference from the mainservice data. According to the embodiment of the present invention, theregion including DATA block B4 to DATA block B7 will be referred to asregion A (=B4+B5+B6+B7).

DATA block B3 and DATA block B8 within the group shown in (a) of FIG. 13collectively correspond to a region having little interference from themain service data. According to the embodiment of the present invention,the region including DATA block B3 and DATA block B8 will be referred toas region B (=B3+B8).

DATA block B2 and DATA block B9 within the group shown in (a) of FIG. 13collectively correspond to a region having a level of interference fromthe main service data greater than that of region B. According to theembodiment of the present invention, the region including DATA block B2and DATA block B9 will be referred to as region C (=B2+B9).

DATA block B0 to DATA block B1 and DATA block B10 to DATA block B11within the group shown in (a) of FIG. 13 collectively correspond to aregion having a level of interference from the main service data greaterthan that of region C. According to the embodiment of the presentinvention, the region including DATA block B0 to DATA block B1 and DATAblock B10 to DATA block B11 will be referred to as region D(=B0+B1+B10+B11).

(b) of FIG. 13 shows an example of dividing a region, which correspondsto the last 38 data packets among the total of 156 data packets within agroup of a data structure after being processed with data interleaving,into 5 extended DATA blocks (extended MH blocks EB0 to EB4). Also,according to the embodiment of the present invention, each of theextended DATA blocks EB1 to EB3 has the length of 16 segments.Additionally, according to the embodiment of the present invention, theextended DATA block EB0 has the length of 15 segments, and the extendedDATA block EB4 has the length of 27 segments.

Furthermore, according to the embodiment of the present invention, theregion including all of the extended DATA blocks EB0 to EB4 shown in (b)of FIG. 13 will be referred to as region E (=EB0+EB1+EB2+EB3+EB4).

(c) of FIG. 13 is identical to an example of overlapping (a) of FIG. 13and (b) of FIG. 13. Herein, the position of the first segment of theextended DATA block EB0 corresponds to the same segment as the secondsegment of DATA block B8. And, with the exception for the first segmentof DATA block B8, all of the remaining segments respectively overlapwith all of the segments of the extended DATA block EB0. Also, allsegments of DATA block B9 respectively overlap with all segments of theextended DATA block EB1, and all segments of DATA block B10 respectivelyoverlap with all segments of the extended DATA block EB2. Finally, allsegments of DATA block B11 overlap with the first 5 segments of theextended DATA block EB3.

In the above-described example, even if the positions overlap in thesame segment, all DATA blocks include only the data corresponding to thefirst 118 data packets of the data group prior to being processed withdata-interleaving, and all extended DATA blocks include only the datacorresponding to the last 38 data packets of the data group prior tobeing processed with data-interleaving.

The mobile service data being allocated to one data group include mobileservice data of both the first mobile mode and the second mobile mode.

The above-described alignment and positioning of the data blocks and theextended data blocks are merely exemplary. And, accordingly, theposition and number of segments being included in the data blocks andthe extended data blocks may vary within a range that does not influenceor deviate from the technical aspects and characteristics of the presentinvention.

FIG. 14 illustrates an exemplary assignment order of data groups beingassigned to one of 5 sub-frames, wherein the 5 sub-frames configure anM/H frame.

For example, the method of assigning data groups may be identicallyapplied to all M/H frames or differently applied to each M/H frame.Furthermore, the method of assigning data groups may be identicallyapplied to all sub-frames or differently applied to each sub-frame. Atthis point, when it is assumed that the data groups are assigned usingthe same method in all sub-frames of the corresponding M/H frame, thetotal number of data groups being assigned to an M/H frame is equal to amultiple of ‘5’.

According to the embodiment of the present invention, a plurality ofconsecutive data groups is assigned to be spaced as far apart from oneanother as possible within the M/H frame. Thus, the system can becapable of responding promptly and effectively to any burst error thatmay occur within a sub-frame.

For example, when it is assumed that 3 data groups are assigned to asub-frame, the data groups are assigned to a 1st slot (Slot #0), a 5thslot (Slot #4), and a 9th slot (Slot #8) in the sub-frame, respectively.FIG. 9 illustrates an example of assigning 16 data groups in onesub-frame using the above-described pattern (or rule). In other words,each data group is serially assigned to 16 slots corresponding to thefollowing numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7, and15. Equation 2 below shows the above-described rule (or pattern) forassigning data groups in a sub-frame.

[Equation 2] j = (4i + 0) mod 16 0 = 0 if i < 4, 0 = 2 else if i < 8,Herein, 0 = 1 else if i < 12, 0 = 3 else.

Herein, j indicates the slot number within a sub-frame. The value of jmay range from 0 to 15. Also, value of i indicates the data groupnumber. The value of i may range from 0 to 15.

In the present invention, a collection of data groups included in an M/Hframe will be referred to as a “parade”. Based upon the RS frame mode,the parade transmits data of at least one specific RS frame.

The mobile service data within one RS frame may be assigned either toall of regions A/B/C/D/E within the corresponding data group, or to atleast one of regions A/B/C/D/E. In the embodiment of the presentinvention, the mobile service data within one RS frame may be assignedeither to all of regions A/B/C/D/E, or to at least one of regions A/Band regions C/D/E. If the mobile service data are assigned to the lattercase (i.e., one of regions A/B and regions C/D/E), the RS frame beingassigned to regions A/B and the RS frame being assigned to regions C/D/Ewithin the corresponding data group are different from one another.

In the description of the present invention, the RS frame being assignedto regions A/B within the corresponding data group will be referred toas a “primary RS frame”, and the RS frame being assigned to regionsC/D/E within the corresponding data group will be referred to as a“secondary RS frame”, for simplicity. Also, the primary RS frame and thesecondary RS frame form (or configure) one parade. More specifically,when the mobile service data within one RS frame are assigned either toall of regions A/B/C/D/E within the corresponding data group, one paradetransmits one RS frame. In this case, also the RS frame will be referredto as a “primary RS frame”. Conversely, when the mobile service datawithin one RS frame are assigned either to at least one of regions A/Band regions C/D/E, one parade may transmit up to 2 RS frames.

More specifically, the RS frame mode indicates whether a paradetransmits one RS frame, or whether the parade transmits two RS frames.Table 2 below shows an example of the RS frame mode.

TABLE 2 RS frame mode (2 bits) Description 00 There is only one primaryRS frame for all group regions(A, B, C, D, E) 01 There are two separateRS frames. Primary RS frame for group regions A and B Secondary RS framefor group regions C, D and E 10 Reserved 11 Reserved

Table 2 illustrates an example of allocating 2 bits in order to indicatethe RS frame mode. For example, referring to Table 2, when the RS framemode value is equal to ‘00’, this indicates that one parade transmitsone RS frame. And, when the RS frame mode value is equal to ‘01’, thisindicates that one parade transmits two RS frames, i.e., the primary RSframe and the secondary RS frame. More specifically, when the RS framemode value is equal to ‘01’, data of the primary RS frame for regionsA/B are assigned and transmitted to regions A/B of the correspondingdata group. Similarly, data of the secondary RS frame for regions C/D/Eare assigned and transmitted to regions C/D/E of the corresponding datagroup.

As described in the assignment of data groups, the parades are alsoassigned to be spaced as far apart from one another as possible withinthe sub-frame. Thus, the system can be capable of responding promptlyand effectively to any burst error that may occur within a sub-frame.

Furthermore, the method of assigning parades may be identically appliedto all sub-frames or differently applied to each sub-frame. According tothe embodiment of the present invention, the parades may be assigneddifferently for each M/H frame and identically for all sub-frames withinan M/H frame. More specifically, the M/H frame structure may vary byMill frame units. Thus, an ensemble rate may be adjusted on a morefrequent and flexible basis.

FIG. 15 illustrates a method for transmitting a primary or secondaryensemble/RS frame through an A, B, C, D, or E region in a data groupaccording to an embodiment of the present invention.

In the case of parade type 1 or 2, a data group has no E region.Accordingly, a conventional mobile broadcast receiver can process aprimary or secondary ensemble/RS frame of parade type 1 or 2.

In the case of parade types 3 to 8, a data group has an E region. Sincedata groups of parade types 3 to 8 each have an E region, a Region ‘E’indicator is set to “1”.

In the case of parade type 3, a primary ensemble/RS frame is transmittedthrough A, B, C, and D regions and a secondary ensemble/RS frame istransmitted through an E region. In this case, an RS frame mode may beset to ‘00’.

In the case of parade type 4, a primary ensemble/RS frame is transmittedthrough A and B regions and a secondary ensemble/RS frame is transmittedthrough C, D, E regions. In this case, an RS frame mode may be set to‘01’.

In the case of parade type 5, a primary ensemble/RS frame is transmittedthrough A, B, C, D, and E regions. In this case, an RS frame mode may beset to ‘01’

In the case of parade type 6, a primary ensemble/RS frame is transmittedthrough A, B, C, and D regions and a secondary ensemble/RS frame istransmitted through an E region. In this case, an RS frame mode may beset to ‘00’. All regions of a data group of parade type 6 are used formobile service data. To indicate this, a full channel indicator is setto ‘1’.

In the case of parade type 7, a primary ensemble/RS frame is transmittedthrough A and B regions and a secondary ensemble/RS frame is transmittedthrough C, D, and E regions. In this case, an RS frame mode may be setto ‘01’. All regions of a data group of parade type 7 are used formobile service data. To indicate this, a full channel indicator is setto 1.

In the case of parade type 8, a primary ensemble/RS frame is transmittedthrough A, B, C, D, and E regions. In this case, an RS frame mode may beset to ‘00’. All regions of a data group of parade type 8 are used formobile service data. To indicate this, a full channel indicator is setto 1.

The conventional mobile broadcast receiver can process ensemble/RSframes transmitted through regions that are underlined in FIG. 15.However, the conventional mobile broadcast receiver cannot processensemble/RS frames transmitted through regions that are underlined inFIG. 15 and cannot provide a corresponding service although it canreceive the ensemble/RS frames.

The set bit value of the RS frame mode and the indicator setting of eachparade type described above are purely exemplary and the presentinvention is not limited to this example.

FIG. 16 illustrates an example of transmitting 3 parades (Parade #0,Parade #1, and Parade #2) to an M/H frame. More specifically, FIG. 16illustrates an example of transmitting parades included in one of 5sub-frames, wherein the 5 sub-frames configure one M/H frame.

When the 1st parade (Parade #0) includes 3 data groups for eachsub-frame, the positions of each data groups within the sub-frames maybe obtained by substituting values ‘0’ to ‘2’ for i in Equation 2. Morespecifically, the data groups of the 1st parade (Parade #0) aresequentially assigned to the 1st, 5th, and 9th slots (Slot #0, Slot #4,and Slot #8) within the sub-frame. Also, when the 2nd parade includes 2data groups for each sub-frame, the positions of each data groups withinthe sub-frames may be obtained by substituting values ‘3’ and ‘4’ for iin Equation 2.

More specifically, the data groups of the 2nd parade (Parade #1) aresequentially assigned to the 2nd and 12th slots (Slot #3 and Slot #11)within the sub-frame.

Finally, when the 3rd parade includes 2 data groups for each sub-frame,the positions of each data groups within the sub-frames may be obtainedby substituting values ‘5’ and ‘6’ for i in Equation 1. Morespecifically, the data groups of the 3rd parade (Parade #2) aresequentially assigned to the 7th and 11th slots (Slot #6 and Slot #10)within the sub-frame.

As described above, data groups of multiple parades may be assigned to asingle MAI frame, and, in each sub-frame, the data groups are seriallyallocated to a group space having 4 slots from left to right. Therefore,a number of groups of one parade per sub-frame (NOG) may correspond toany one integer from ‘1’ to ‘8’. Herein, since one M/H frame includes 5sub-frames, the total number of data groups within a parade that can beallocated to an M/H frame may correspond to any one multiple of ‘5’ranging from ‘5’ to ‘40’.

Parade #1 is a parade of parade type 4 and includes an E region in itsdata group. From this, it can be seen that a parade including a CMM datagroup and a parade including an SFCMM data group may be multiplexed andtransmitted within one subframe.

FIG. 17 illustrates a detailed block diagram of the signaling encoderaccording to the present invention.

Referring to FIG. 17, the signaling encoder includes a TPC encoder 561,an FIC encoder 562, a block interleaver 563, a multiplexer 564, asignaling randomizer 565, and a PCCC (Parallel ConcatenatedConvolutional Code) encoder 566.

The TPC encoder 561 receives 10-bytes of TPC data and performs(18,10)-RS encoding on the 10-bytes of TPC data, thereby adding 8 bytesof RS parity data to the 10 bytes of TPC data. The 18 bytes ofRS-encoded TPC data are outputted to the multiplexer 564.

The FIC encoder 562 receives 37-bytes of FIC data and performs(51,37)-RS encoding on the 37-bytes of FIC data, thereby adding 14 bytesof RS parity data to the 37 bytes of FIC data. Thereafter, the 51 bytesof RS-encoded FIC data are inputted to the block interleaver 563,thereby being interleaved in predetermined block units. Herein, theblock interleaver 563 corresponds to a variable length blockinterleaver. The block interleaver 563 interleaves the FIC data withineach sub-frame in TNoG(column)×51(row) block units and then outputs theinterleaved data to the multiplexer 564. Herein, the TNoG corresponds tothe total number of data groups being assigned to a sub-frame. The blockinterleaver 563 is synchronized with the first set of FIC data in eachsub-frame.

The block interleaver 563 writes 51 bytes of incoming (or inputted) RScodewords in a row direction (i.e., row-by-row) and left-to-right andup-to-down directions and reads 51 bytes of RS codewords in a columndirection (i.e., column-by-column) and left-to-right and up-to-downdirections, thereby outputting the RS codewords.

The multiplexer 564 multiplexes the RS-encoded TPC data from the TPCencoder 561 and the block-interleaved FIC data from the blockinterleaver 563 along a time axis. Then, the multiplexer 564 outputs 69bytes of the multiplexed data to the signaling randomizer 565. Thesignaling randomizer 565 randomizes the multiplexed data and outputs therandomized data to the iterative turbo encoder 566. The signalingrandomizer 565 may use the same generator polynomial of the randomizerused for mobile service data. Also, initialization occurs in each datagroup.

The PCCC encoder 566 corresponds to an inner encoder performingiterative turbo encoding in a PCCC method on the randomized data (i.e.,signaling information data).

For example, if the PCCC encoder 566 performs encoding of data at acoding rate of 1/4, 69 bytes applied to the PCCC encoder 566 areextended to 276 bytes by the iterative turbo-encoding process, such thatthe PCCC encoder 566 outputs the resultant 276 bytes. The 276 bytesgenerated from the PCCC encoder 566 are transferred to the groupformatter, such that they are inserted into a signaling information areaof a corresponding data group.

FIG. 18 illustrates how a block interleaver in a signaling encoderoperates to interleave FIC data according to an embodiment of thepresent invention.

A variable length Block interleaver consisting of 51 columns (of bytes)and a number of rows equal to TNoG shall be employed to interleave theRS encoded FIC data within each M/H Sub-Frame. The Block interleavershall write the incoming RS codewords of 51 bytes row-by-row from leftto right and top-to-bottom and shall output the data in units of 51bytes by reading column by column from top-to-bottom and left-to-right,as shown FIG. 18.

The TNoG shall be identical for all Sub-Frames in an M/H Frame.

The first byte in the FIC Block interleaver shall be the first FIC databyte of each Sub-Frame. The FIC block interleaver interleaves one blockof FIC data across each subframe.

FIG. 19 illustrates a syntax structure of an FIC chunk header accordingto an embodiment of the present invention.

Herein, the FIC chunk header signals a non-backward compatible majorprotocol version change in a corresponding FIC chunk and also signals abackward compatible minor protocol version change. Furthermore, the FICchunk header also signals the length for an extension of an FIC chunkheader, the length for an extension of an ensemble loop header, and thelength for an extension of a mobile service loop that can be generatedby a minor protocol version change.

According to an embodiment of the present invention, a receiver (orreceiving system) that can adopt the corresponding minor protocolversion change may process the corresponding extension field, whereas alegacy (or conventional) receiver that cannot adopt the correspondingminor protocol version change may skip the corresponding extension fieldby using each of the corresponding length information. For example, incase of a receiving system that can accept the corresponding minorprotocol version change, the directions given in the correspondingextension field may be known. Furthermore, the receiving system mayperform operations in accordance with the directions given in thecorresponding extension field.

According to an embodiment of the present invention, a minor protocolversion change in the FIC chunk is performed by inserting additionalfields at the respective end portion of the FIC chunk header, theensemble loop header, and the mobile service loop included in theprevious minor protocol version FIC chunk. According to an embodiment ofthe present invention, in any other case, or when the length of theadditional fields cannot be expressed (or indicated) by each extensionlength within the FIC chunk header, or when a specific field within theFIC chunk payload is missing (or cannot be found), or when the number ofbits being assigned to the corresponding field or the definition of thecorresponding field is changed (or altered), the major protocol versionof the corresponding FIC chunk is updated.

Also, the FIC chunk header signals whether the data of a correspondingFIC chunk payload carry mapping information between an ensemble and amobile service within the current M/H frame, or whether the data of acorresponding FIC chink payload carry mapping information between anensemble and a mobile service within the next M/H frame. Furthermore,the FIC chunk header also signals the number of transport stream IDs ofa mobile service through which the current FIC chunk is beingtransmitted and the number of ensembles being transmitted through thecorresponding mobile service.

Accordingly, for this, the FIC chunk header may include anFIC_major_protocol_version field, an FIC_minor_protocol_version field,an FIC_chunk_header_extension_length field, anensemble_loop_header_extension_length field, anM/H_service_loop_extension_length field, a current_next_indicator field,a transport_stream_id field, a num_MH_(—)1.1_ensembles field and anum_ensembles field.

The FIC_major_protocol_version field corresponds to a 2-bit unsignedinteger field that represents the major version level of a FIC chunksyntax. A change in the major version level shall indicate a change in anon-backward-compatible level. When the FIC_major_protocol_version fieldis updated, legacy (or conventional) receivers, which can process theprior major protocol version of an FIC chunk protocol, shall avoidprocessing the FIC chunk.

The FIC_minor_protocol_version field corresponds to a 3-bit unsignedinteger field that represents the minor version level of an FIC chunksyntax. When it is assumed that the major version level remains thesame, a change in the minor version level shall indicate a change in abackward-compatible level. More specifically, when theFIC_minor_protocol_version field is updated, legacy (or conventional)receivers, which can process the same major version of the FIC chunkprotocol, may process a portion of the FIC chunk.

The minor protocol versioning is used so that a conventional mobilereceiving device can ignore the SFCMM Ensemble/Service portion of theFIC-Chunk data structure, and avoid any malfunction due to the presenceof extended data.

The FIC_Chunk_header_extension_length field corresponds to a 3-bitunsigned integer field identifying the length of FIC chunk headerextension bytes, which are generated by the minor protocol versionupdate of the corresponding FIC chunk. Herein, the extension bytes areappended (or added) at the end of the corresponding FIC chunk header.

In an embodiment of the present invention, when anFIC_Chunk_header_extension_length field is set to ‘001’, this indicatesthat a 1-byte extension is present in the FIC chunk header. In thiscase, the conventional mobile broadcast receiver (i.e., the CMMreceiving device) skips the extended field in the FIC chunk headeraccording to the value of the FIC_Chunk_header_extension_length field.For example, since a num_MH1.1_ensembles field in the FIC chunk headeris a field added to the FIC chunk header when the FIC chunk header isextended, the conventional mobile broadcast receiver need not processthis field. In this case, the conventional mobile broadcast receiverprocesses only the CMM ensemble or service related fields among thefields of the FIC chunk payload and may skip processing the SFCMMensemble or service related fields added to the FIC chunk payload

That is, through the FIC_Chunk_header_extension_length field value of‘001’, the conventional mobile broadcast receiver determines that itshould skip one byte prior to the num_ensembles field and a new mobilebroadcast receiver determines that one byte field to be read by the newmobile broadcast receiver is present prior to the num_ensembles field.

The ensemble_header_extension_length field corresponds to a 3-bitunsigned integer field identifying the length of the ensemble headerextension bytes, which are generated by the minor protocol versionupdate of the corresponding FIC chunk. Herein, the extension bytes areappended (or added) at the end of the corresponding ensemble loopheader.

Also, the M/H_service_loop_extension_length field corresponds to a 4-bitunsigned integer field identifying the length of the ensemble headerextension bytes, which are generated by the minor protocol versionupdate of the M/H service loop. Herein, the extension bytes are appended(or added) at the end of the corresponding M/H service loop.

For example, it is assumed that the FIC chunk includes 2 ensembles(i.e., ensemble 0 and ensemble 1), more specifically, it is assumed thattwo mobile services are transmitted through ensemble 0, and one mobileservice is transmitted through ensemble 1. At this point, when the minorprotocol version of the FIC chunk is changed, and the FIC chunk headeris expanded by 1 byte, the FIC_chunk_header_extension_length field ismarked as ‘001’. In this case, a 1-byte expansion field (i.e.,FIC_Chunk_header_extension_bytes field) is added at the end of the FICchunk header. Also, the legacy receiver skips the 1-byte expansionfield, which is added at the end of the FIC chunk header, withoutprocessing the corresponding expansion field.

Additionally, when the ensemble loop header within the FIC chunk isexpanded by 2 bytes, the ensemble_loop_header_extension_length field ismarked as ‘010’. In this case, a 2-byte expansion field (i.e.,Ensemble_loop_header_extension_bytes field) is respectively added at theend of the ensemble 0 loop header and at the end of the ensemble 1 loopheader. Also, the legacy receiver skips the 2-byte expansion fields,which are respectively added at the end of the ensemble 0 loop headerand at the end of the ensemble 1 loop header, without processing thecorresponding 2-byte expansion fields.

Furthermore, when the mobile service loop of the FIC chunk is expandedby 1 byte, the M/H_service_loop_extension_length field is marked as‘001’. In this case, a 1-byte expansion field (i.e.,M/H_service_loop_extension_bytes field) is respectively added at the endof 2 mobile service loops being transmitted through ensemble 0 loop andat the end of 1 mobile service loop being transmitted through theensemble 1 loop. And, the legacy receiver skips the 1-byte expansionfields, which are respectively added at the end of 2 mobile serviceloops being transmitted through ensemble 0 loop and at the end of 1mobile service loop being transmitted through the ensemble 1 loop,without processing the corresponding 1-byte expansion fields.

As described above, when the FIC_minor_protocol version field ischanged, a legacy (or conventional) receiver (i.e., a receiver thatcannot adopt the minor protocol version change in the corresponding FICchunk) processes the fields apart from the extension field. Thereafter,the legacy receiver uses the FIC_chunk_header_extension_length field,the ensemble_loop_header_extension_length field, and theM/H_service_loop_extension_length field, so as to skip the correspondingexpansion fields without processing the corresponding fields. When usinga receiving system that can adopt the corresponding minor protocolversion change of the FIC chunk, each length field is used to processeven the corresponding expansion field.

The current_next_indicator field corresponds to a 1-bit indicator,which, when set to ‘1’, indicates that the corresponding FIC chunk iscurrently applicable. Alternatively, when the current_next_indicatorfield is set to ‘0’, the current_next_indicator field indicates that thecorresponding FIC chunk will be applicable for the next M/H frame.Herein, when the current_next_indicator field is set to ‘0’, the mostrecent version of the FIC chunk being transmitted with thecurrent_next_indicator field set to ‘1’ shall be currently applicable.More specifically, when the current_next_indicator field value is set to‘1’, this indicates that the corresponding FIC chunk transmits thesignaling data of the current M/H frame. Further, when thecurrent_next_indicator field value is set to ‘0’, this indicates thatthe corresponding FIC chunk transmits the signaling data of the next M/Hframe. When reconfiguration occurs, wherein the mapping informationbetween the ensemble within the current M/H frame and the mobile servicediffers from the ensemble within the next M/H frame and the mobileservice, the M/H frame prior to reconfiguration is referred to as thecurrent M/H frame, and the M/H frame following reconfiguration isreferred to as the next M/H frame.

The transport_stream_id field corresponds to a 16-bit unsigned integernumber field, which serves as a label for identifying the correspondingM/H broadcast. The value of the corresponding transport_stream_id fieldshall be equal to the value of the transport_stream_id field included inthe program association table (PAT) within the MPEG-2 transport streamof a main ATSC broadcast.

The num_MH1.1_ensembles field corresponds to an 8-bit unsigned integerfield, the value of which shall equal the number of SFCMM Ensemblescarried through this digital Broadcast that are not available to CMMreceiver devices, including the SFCMM Ensembles where the value of thePRC for the corresponding M/H Parades is greater than 0 and that do nothave any M/H Groups in the M/H Frame to which this FIC-Chunk refers. Theconventional mobile broadcast receiver may not process this field andskip it. The term of ‘MH1.1’ is defined same as SFCMM.

The num_ensembles field corresponds to an 8-bit unsigned integer field,which indicates the number of CMM ensembles carried through thecorresponding physical transmission channel.

FIG. 20 illustrates an exemplary syntax structure of an FIC chunkpayload according to an embodiment of the present invention. For eachensemble and MH1.1 ensemble corresponding to the num_ensembles field andnum_MH1.1_ensembles field value within the FIC chunk header of FIG. 19,the FIC chunk payload includes configuration information of eachensemble/MH1.1 ensemble and information on mobile services beingtransmitted through each ensemble.

The FIC chunk payload consists of an ensemble loop and a mobile serviceloop below the ensemble loop. The FIC chunk payload enables the receiverto determine through which ensemble a requested (or desired) mobileservice is being transmitted. (This process is performed via mappingbetween the ensemble_id field and the M/H_service_id field.) Thus, thereceiver may receive RS frames belonging to the corresponding ensemble.

In order to do so, the ensemble loop of the FIC chunk payload mayinclude an ensemble_id field, an ensemble_protocol_version field, anSLT_ensemble_indicator field, a GAT_ensemble_indicator field, anMH_service_signaling_channel_version field, and a num_M/H_servicesfield, which are collectively repeated as many times as thenum_ensembles field value. The mobile service loop may include anMH_service_id field, a service_span field, an MH_service_status field,and an SP_indicator field, which are collectively repeated as many timesas the num_M/H_services field.

The ensemble_id field corresponds to an 8-bit unsigned integer field,which indicates a unique identifier of the corresponding ensemble. Forexample, the ensemble_id field may be assigned with values within therange ‘0x00’ to ‘0x7F’. The ensemble_id field group (or associate) themobile services with the respective ensemble. Herein, it is preferablethat the value of the ensemble_id field is derived from the parade_idfield carried (or transmitted) through the TPC data. If thecorresponding ensemble is transmitted through a primary RS frame, themost significant bit is set to ‘0’, and the remaining least significantbits are used as the parade_id field value of the corresponding parade.Meanwhile, if the corresponding ensemble is transmitted through asecondary RS frame, the most significant bit is set to ‘0’, and theremaining least significant bits are used as the parade_id field valueof the corresponding parade.

The ensemble_protocol_version field corresponds to a 5-bit field, whichspecifies a version of the corresponding ensemble structure.

The SLT_ensemble_indicator field is a 1-bit field, which indicateswhether or not the SLT is being transmitted to the service signalingchannel of the corresponding ensemble. For example, when theSLT_ensemble_indicator field value is equal to ‘1’, this may indicatethat the SLT is being transmitted to the service signaling channel. Onthe other hand, when the SLT_ensemble_indicator field value is equal to‘0’, this may indicate that the SLT is not being transmitted.

The GAT_ensemble_indicator field is also a 1-bit field, which indicateswhether or not the GAT is being transmitted to the service signalingchannel of the corresponding ensemble. For example, when theGAT_ensemble_indicator field value is equal to ‘1’, this may indicatethat the GAT is being transmitted to the service signaling channel. Onthe other hand, when the GAT_ensemble_indicator field value is equal to‘0’, this may indicate that the GAT is not being transmitted.

The MH_service_signaling_channel_version field corresponds to a 5-bitfield, which indicates a version number of the service signaling channelof the corresponding ensemble.

The num_M/H_services field corresponds to an 8-bit unsigned integerfield, which represents the number of mobile (i.e., M/H) servicescarried through the corresponding M/H ensemble.

For example, when the minor protocol version within the FIC chunk headeris changed, and when an extension field is added to the ensemble loopheader, the corresponding extension field is added immediately after thenum_M/H_services field. According to anther embodiment of the presentinvention, if the num_M/H_services field is included in the mobileservice loop, the corresponding extension field that is to be added inthe ensemble loop header is added immediately after theM/H_service_configuration_version field.

The M/H_service_id field of the mobile service loop corresponds to a16-bit unsigned integer number, which identifies the corresponding M/Hservice. The value (or number) of the M/H_service_id field shall beunique within the mobile (M/H) broadcast. When an M/H service hascomponents in multiple M/H ensembles, the set of IP streamscorresponding to the service in each ensemble shall be treated as aseparate service for signaling purposes, with the exception that theentries for the corresponding services in the FIC shall all have thesame M/H_service_id field value. Thus, the same M/H_service_id fieldvalue may appear in more than one num_ensembles loop. And, accordingly,the M/H_service_id field shall represent the overall combined service,thereby maintaining the uniqueness of the M/H_service_id field value.

The multi_ensemble_service field is a two-bit enumerated field thatshall identify whether this M/H Service is carried across more than oneM/H Ensemble. Also, this field identifies whether the M/H Service can berendered meaningfully with only the portion of the M/H Service carriedthrough this M/H Ensemble.

The MH_service_status field is a two-bit enumerated field that shallidentify the status of this M/H Service. The most significant bitindicates whether this M/H Service is active (when set to 1) or inactive(when set to 0) and the least significant bit indicates whether this M/HService is hidden (when set to 1) or not (when set to 0).

The SP_indicator field is a one-bit field that indicates, when set,service protection is applied to at least one of the components neededto provide a meaningful presentation of this M/H Service.

The FIC_chunk_stuffing field indicates that stuffing may exist in anFIC-Chunk. The number of stuffing bytes shall be the minimum numberneeded to make the length of the FIC-Chunk evenly divisible by 35.

Fields including SFCMM ensemble related information are added to an FICpayload included in the extended signaling data. The descriptions ofthese fields are similar to those of the fields described above.

FIG. 21 illustrates mapping of an FIC chunk to an FIC segment deliveryunit according to an embodiment of the present invention.

Within an M/H Frame, the total number of FIC-Segments is equal to(TNoG*5), which provides (37*TNoG*5) bytes for FIC-Chunk delivery. EachFIC-Segment has a two-byte header and 35 bytes for payload.

Each FIC-Chunk instance to be transmitted shall be divided into a numberof delivery units of size 35 bytes in length. The number of deliveryunits is determined by the size of the FIC-Chunk instance, which in turnis determined by the number of M/H Ensembles and the number of M/HServices present in the M/H Broadcast. Each delivery unit shall bepacked into an FIC-Segment for transmission.

FIG. 22 illustrates an exemplary syntax structure of an FIC segmentheader according to an embodiment of the present invention.

Herein, the FIC segment header may include a FIC_segment_type field, anFIC_chunk_major_protocol_version field, a current_next_indicator field,an error_indicator field, an FIC_segment_num field, and anFIC_last_segment_num field. Each field will now be described as follows.

The FIC_segment_type field corresponds to a 2-bit field, which, when setto ‘00’ indicates that the corresponding FIC segment is carrying aportion of an FIC chunk. Alternatively, when the FIC_segment_type fieldis set to ‘11’, the FIC_segment_type field indicates that thecorresponding FIC segment is a null FIC segment, which transmitsstuffing data. Herein, the remaining values are reserved for future use.

The FIC_Chunk_major_protocol_version field corresponds to a 2-bit field,which indicates a major protocol version of the corresponding FIC chunk.At this point, the value of the FIC_Chunk_major_protocol_version fieldshould be the same as the value of the FIC_major_protocol_version fieldwithin the corresponding FIC chunk header. Since reference may be madeto the description of the FIC chunk header shown in FIG. 19, a detaileddescription of the major protocol version of the FIC chunk syntax willbe omitted for simplicity.

The current_next_indicator field corresponds to a 1-bit indicator,which, when set to ‘1’, shall indicate that the corresponding FICsegment is carrying a portion of the FIC chunk, which is applicable tothe current M/H frame. Alternatively, when the value of thecurrent_next_indicator field is set to ‘0’, the current_next_indicatorfield shall indicate that the corresponding FIC segment is carrying aportion of the FIC chunk, which will be applicable for the next M/Hframe.

The error_indicator field corresponds to a 1-bit field, which indicateswhether or not an error has occurred in the corresponding FIC segmentduring transmission. Herein, the error_indicator field is set to ‘1’,when an error has occurred. And, the error_indicator field is set to‘0’, when an error does not exist (or has not occurred). Morespecifically, during the process of configuring the FIC segment, when anon-recovered error exists, the error_indicator field is set to T. Morespecifically, the error_indicator field enables the receiving system torecognize the existence (or presence) of an error within thecorresponding FIC segment.

The FIC_segment_num field corresponds to a 4-bit unsigned integer numberfield, which indicates a number of the corresponding FIC segment. Forexample, if the corresponding FIC segment is the first FIC segment ofthe FIC chunk, the value of the FIC_segment_num field shall be set to‘0x0’. Also, if the corresponding FIC segment is the second FIC segmentof the FIC chunk, the value of the FIC_segment_num field shall be set to‘0x1’. More specifically, the FIC_segment_num field shall be incrementedby one with each additional FIC segment in the FIC chunk. Herein, if theFIC chunk is divided into 4 FIC segments, the FIC_segment_num fieldvalue of the last FIC segment within the FIC chunk will be indicated as‘0x3’.

The FIC_last_segment_num field corresponds to a 4-bit unsigned integernumber field, which indicates the number of the last FIC segment (i.e.,the FIC segment having the highest FIC_segment_num field value) within acomplete FIC chunk.

In the conventional method, FIC segment numbers are sequentiallyassigned (or allocated) for each FIC segment within one sub-frame.Therefore, in this case, the last FIC segment number always matches withthe TNoG (i.e., the last FIC segment number is always equal to theTNoG). However, when using the FIC number assignment method according tothe present invention, the last FIC segment number may not always matchwith the TNoG. More specifically, the last FIC segment number may matchwith the TNoG, or the last FIC segment number may not match with theTNoG. The TNoG represents a total number of data groups that areallocated (or assigned) to a single sub-frame. For example, when theTNoG is equal to ‘6’, and when the FIC chunk is divided into 8 FICsegments, the TNoG is equal to ‘6’, and the last FIC segment number is‘8’.

According to another embodiment of the present invention, the null FICsegment may be identified by using the value of the FIC_segment_numfield within the FIC segment header. More specifically, since an FICsegment number is not assigned to the null FIC segment, the transmittingsystem allocates null data to the FIC_segment_num field value of thenull FIC segment, and the receiving system may allow the FIC segmenthaving null data assigned to the FIC_segment_num field value to berecognized as the null FIC segment. Herein, instead of the null data,data pre-arranged by the receiving system and the transmitting systemmay be assigned to the FIC_segment_num field value, instead of the nulldata.

As described above, the FIC chunk is divided into a plurality of FICsegments, thereby being transmitted through a single sub-frame or beingtransmitted through multiple sub-frames. Also, FIC segments divided froma single FIC chunk may be transmitted through a single sub-frame, or FICsegments divided from multiple single FIC chunks may be transmittedthrough a single sub-frame. At this point, the number assigned to eachFIC segment corresponds to a number within the corresponding FIC chunk(i.e., the FIC_seg_number value), and not the number within thecorresponding sub-frame. Also, the null FIC segment may be transmittedfor aligning the boundary of the M/H frame and the boundary of the FICchunk. At this point, an FIC segment number is not assigned to the nullFIC segment.

As described above, one FIC chunk may be transmitted through multiplesub-frames, or multiple FIC chunks may be transmitted through a singlesub-frame. However, according to the embodiment of the presentinvention, the FIC segments are interleaved and transmitted in sub-frameunits.

FIG. 23 is a block diagram of a digital broadcast receiver according toan embodiment of the present invention.

The digital broadcast receiver includes an ATSC-M/H baseband processor2100, an ATSC-MH service demultiplexer 2300, an ATSC-MH IP adaptationmodule 2500, a common IP module 2700, and an application module 2900.The digital broadcast receiver may also include an operation controller2960, an EPG manager 2970, an application manager 2980, a presentationmanager 2990, and a UI manager 2996.

The ATSC-M/H baseband processor 2100 includes a baseband operationcontroller 2110, a tuner 2120, a demodulator 2130, an equalizer 2140, aknown sequence detector 2150, a block decoder 2160, a baseband signalingdecoder 2170, a primary RS frame decoder 2180, and a secondary RS framedecoder 2190.

The baseband operation controller 2110 controls the overall operation ofthe baseband module of the receiver. In an embodiment, all components ofthe ATSC-M/H baseband processor 2100 are controlled by the basebandoperation controller 2110.

The tuner 2120 functions to tune the receiver to a specific frequencysignal carrying a digital broadcast signal. The tuner 2120 down-convertsthe received frequency signal into an Intermediate Frequency (IF) signaland outputs the IF signal to the demodulator 2130 and the known sequencedetector 2150.

The demodulator 2130 performs automatic gain control, carrierrestoration, timing restoration, and the like on a digital IF signal ofthe pass band input from the tuner 2120 to create a baseband signal andthen outputs the baseband signal to the equalizer 2140 and the knownsequence detector 2150. The demodulator 2130 may perform timingrestoration or carrier restoration using a symbol sequence of known datainput from the known sequence detector 2150. That is, the demodulator2130 may demodulate broadcast data using a demodulation result of dataknown to the receiver, thereby increasing demodulation performance.

The equalizer 2140 receives the demodulated signal from the demodulator2130 and compensates for channel distortion that has occurred duringtransmission and then outputs the resulting signal to the block decoder2160. The equalizer 2140 may use a known data symbol sequence input fromthe known sequence detector 2150 to improve equalization performance.The equalizer 2140 may also receive feedback of the decoding result toimprove equalization performance.

The known sequence detector 2150 receives data input to and output fromthe demodulator 2130, i.e., data that has not demodulated or data thathas been partially demodulated and detects the position of known datainserted by the transmitting side. The known sequence detector 2150outputs a known data sequence decoded at the detected position of theknown data, together with the detected position information of the knowndata, to the demodulator 2130 and the equalizer 2140. The known sequencedetector 2150 may output information, which enables the block decoder2160 to distinguish mobile service data that was subjected to additionalencoding at the transmitting side and data that was not subjected toadditional encoding at the transmitting side, to the block decoder 2160.

The block decoder 2160 performs the reverse processes of block encodingand trellis encoding, i.e., block decoding and trellis decoding, on theinput channel-equalized data input from the equalizer 2140 when theinput channel-equalized data is data (i.e., data in an RS frame orsignaling data) that was subjected to block encoding and trellisencoding at the transmitting side. The block decoder 2160 performs onlytrellis decoding on the input channel-equalized data input from theequalizer 2140 when the input channel-equalized data is data (i.e., mainservice data) that was subjected to trellis encoding but was notsubjected to block encoding at the transmitting side.

The baseband signaling decoder 2170 decodes signaling data that wassubjected to both block encoding and trellis encoding when the signalingdata is input to the baseband signaling decoder 2170 after beingchannel-equalized by the equalizer 214. Here, the decoded signaling dataincludes a transmission parameter. In an embodiment of the presentinvention, the signaling data may be Transmission Parameter Channel(TPC) data. Transmission parameters included in the signaling data mayinclude information indicating whether or not TPC data has been changed(for example, updated), information indicating whether the digitalbroadcast signal has been transmitted in an SFCMM or in a CMM,information indicating the number of mobile service data packets thatare additionally included in one data group, and information indicatingwhether or not data blocks included in each of adjacent data groupsconstitute one SCCC block.

The primary RS frame decoder 2180 receives only RS-encoded and/orCRC-encoded mobile service data among data output from the block decoder2160. The primary RS frame decoder 2180 performs the inverse of theprocess of the RS frame encoder in the transmission system. The primaryRS frame decoder 2180 also corrects errors in the RS frame and combinesa number of error-corrected data groups to create an RS frame. That is,the primary RS frame decoder 2180 decodes a primary RS frame includingdata for actual broadcast service.

The secondary RS frame decoder 2190 receives only RS-encoded and/orCRC-encoded mobile service data among data output from the block decoder2160. The secondary RS frame decoder 2190 performs the inverse of theprocess of the RS frame encoder in the transmission system. Thesecondary RS frame decoder 2190 also corrects errors in the RS frame andcombines a number of error-corrected data groups to create an RS frame.That is, the secondary RS frame decoder 2190 decodes a primary RS frameincluding additional data for broadcast service. Although the primary RSframe decoder 2180 and the secondary RS frame decoder 2190 areseparately illustrated, both the primary RS frame decoder 2180 and thesecondary RS frame decoder 2190 may be included in an RS frame decoderwhich can separately perform primary RS frame decoding and secondary RSframe decoding.

The ATSC-MH service demultiplexer 2300 includes an FIC segment buffer2310, an FIC segment parser 2320, an FIC chunk parser 2330, an M/Hservice signaling section parser 2340, an M/H service signaling sectionbuffer 2350, a service manager 2360, and a service map/guide DB 2370.

The FIC segment buffer 2310 serves to buffer an FIC-segment group in ade-interleaved and RS-decoded M/H subframe received from the basebandsignaling decoder 2170.

The FIC segment parser 2320 serves to extract, analyze, and process aheader of each FIC segment stored in the FIC segment buffer 2310. TheCMM receiver ignores an SFCMM related field through anFIC_chunk_major_protocol_version or FIC_chunk_minor_protocol_versionvalue included in the header of the FIC segment obtained in thisprocess. The CMM receiver also skips an added field in the headerthrough an FIC_chunk_header_extension_length included in the header ofthe FIC segment.

The FIC chunk parser 2330 serves to restore and analyze/process an FICchunk data structure in FIC segments analyzed by the FIC Segment Parser2320.

The M/H service signaling section parser 2340 serves to analyze/processtable sections of an M/H service signaling channel transmitted through aUDP/IP stream.

The M/H service signaling section buffer 2350 buffers table sections ofan M/H service signaling channel to be processed by the M/H servicesignaling section parser 2340.

The service manager 2360 constructs a service map signaling datacollected from the FIC chunk parser 2330 and the M/H service signalingsection parser 2340 and creates a program guide using a service guide.The service manager 2360 also serves to control the baseband operationcontroller 2110 so as to receive a desired M/H service according to auser input and to allow a program guide to be displayed according to auser input.

The service map/guide DB 2370 serves to store the service map and theservice guide created by the service manager 2360 and to extract andtransfer service related data required for each component to thecomponent according to inputs from the service manager 2360 and the EPGmanager 2970.

The ATSC-MH IP adaptation module 2500 includes a primary RS frame buffer2510, a secondary RS frame buffer 2520, an M/H Transport stream Packet(TP) buffer 2530, and an M/H TP parser 2540.

The primary RS frame buffer 2510 serves to buffer an RS frame receivedfrom the primary RS frame decoder 2180 and to transfer each received RSframe row by row to the M/H TP buffer 2530.

The secondary RS frame buffer 2520 serves to buffer an RS frame receivedfrom the secondary RS frame decoder 2190 and to transfer each receivedRS frame row by row to the M/H TP buffer 2530. The primary RS framebuffer 2510 and the secondary RS frame buffer 2520 may be physicallyconstructed as one buffer.

The M/H TP buffer 2530 serves to extract and buffer an M/H TPcorresponding to each row of the RS frame.

The M/H TP parser 2540 serves to analyze a header corresponding to thefirst 2 bytes to restore an IP datagram.

The common IP module 2700 includes an IP datagram buffer 2710, an IPdatagram header parser 2713, a descrambler 2720, a UDP datagram buffer2730, a UDP datagram parser 2733, an RTP/RTCP datagram buffer 2740, anRTP/RTCP datagram parser 2743, an NTP datagram buffer 2750, an NTPdatagram parser 2753, a SvcProtection stream buffer 2760, aSvcProtection stream handler 2763, an ALV/LCT stream buffer 2770, anALV/LCT stream parser 2773, a decompressor 2780, a key storage 2783, anXML parser 2785, and an FDT handler 2787.

The IP datagram buffer 2710 buffers an encapsulated IP datagram receivedthrough the M/H TP.

The IP datagram header parser 2713 restores IP datagrams and analyzes aheader of each datagram. In an embodiment, the operation of the IPdatagram header parser 2713 is performed through the service manager2360.

The descrambler 2720 functions to descramble data of a scrambled payloadincluded in the received IP datagram using an encryption key receivedfrom the SvcProtection stream handler 2763.

The UDP datagram buffer 2730 serves to buffer a UDP datagram receivedthrough the IP datagram.

The UDP datagram parser 2733 functions to restore the UDP datagram andto analyze and process a restored UDP header.

The RTP/RTCP datagram buffer 2740 buffers a datagram of an RTP/RTCPstream received through a UDP/IP stream.

The RTP/RTCP datagram parser 2743 serves to restore, analyze, andprocess a datagram of an RTP/RTCP stream.

The NTP datagram buffer 2750 buffers a datagram of a network timeprotocol stream received through a UDP/IP stream.

The NTP datagram parser 2753 serves to restore, analyze, and process adatagram of a network time protocol stream.

The SvcProtection stream buffer 2760 buffers data, such as a key valuefor descrambling required for a service protection function, receivedthrough a UDP/IP stream.

The SvcProtection stream handler 2763 processes data such as a key valuefor descrambling required for the service protection function. Dataoutput from the SvcProtection stream handler 2763 is transferred to thedescrambler 2720.

The ALV/LCT stream buffer 2770 buffers ALC/LCT data received through aUDP/IP stream.

The ALV/LCT stream parser 2773 functions to restore ALC/LCT datareceived through a UDP/IP stream and to analyze a header and a headerextension of the ALC/LCT data.

When the decompressor 2780 receives a compressed file, the decompressor2780 performs a process for decompressing the file.

The key storage 2783 stores a key message used for the serviceprotection function that has been restored by the SvcProtection streamhandler.

The XML parser 2785 serves to analyze an XML document received throughan ALC/LCT session and to transfer the analyzed data to appropriatemodules such as the FDT handler 2787 and the SG handler 2950.

The FDT handler 2787 analyzes and processes a file description tablereceived through an ALC/LCT session.

The application module 2900 includes an A/V decoder 2910, a file decoder2920, a file storage 2930, an M/W engine 2940, and a Service Guide (SG)handler 2950.

The A/V decoder 2910 functions to decode compressed audio/video datareceived through the RTP/RTCP datagram Parser 2743 and to process thedecoded data for presentation to the user.

The file decoder 2920 functions to decode the file restored by theALV/LCT stream parser 2773.

The file storage 2930 functions to store the file decoded by the filedecoder 2920 and to provide the file to another module when needed.

The M/W engine 2940 processes data such as a file received through aFLUTE session or the like and provides the data to the presentationmanager 2990.

The Service Guide (SG) handler 2950 performs a process for collectingand analyzing service guide data received in an XML document format andproviding the service guide data to the EPG manager 2970.

The operation controller 2960 performs an operation for processing auser command received through a UI Manager 2996 and performs amanagement operation to enable a manger of each module, required duringthe procedure for processing the command, to perform a correspondingaction.

The EPG manager 2970 performs a management operation to enable acorresponding EPG to be displayed according to user input using EPG datareceived through the service guide handler 2950.

The application manager 2980 performs overall management associated withprocessing of application data received in the form of an object, afile, or the like.

The presentation manager 2990 processes data received from the A/Vdecoder 2910, the M/W engine 2940, the EPG manager 2950, and the like toenable presentation of the service to the user. This process may beperformed under control of the operation controller 2960.

The UI manager 2996 transfers a user input received through the userinterface to the operation controller 2960 and performs a managementoperation to start a process for a service required by the user.

The names of the modules of the receiver described above may be changed.Specific modules may be omitted or added depending on the system.

FIG. 24 illustrates a block view of the signaling decoder according toan embodiment of the present invention. The signaling decoder performsiterative turbo decoding and RS-decoding on the data of the signalinginformation region among the equalized data. Thereafter, thetransmission parameter (i.e., TPC data) obtained as a result of theabove-described process is outputted to the baseband operationcontroller, and the FIC data are outputted to an upper layer.

For this operation, the signaling decoder may include an iterative turbodecoder 7111, a derandomizer 7112, a demultiplexer 7113, an RS decoder7114, a block deinterleaver 7115, and an RS decoder 7116.

FIG. 25 illustrates a method in which a CMM receiver and an SFCMMreceiver process data according to FIC header information according toan embodiment of the present invention.

SFCMM may be expressed as MH 1.1 and CMM may be expressed as MH 1.0 forease of explanation.

As shown in FIG. 25( a), when a CMM receiver parses an FIC header havingan extended field, the CMM receiver determines, through anFIC_chunk_minor_protocol_version value, that an extension for asignaling structure for an SFCMM is present in the FIC. Using such minorprotocol versioning, the CMM ignores a portion for SFCMMensemble/service in the FIC data structure. Through this operation, itis possible to prevent malfunction due to presence of extended data.More specifically, the CMM receiver determines that an extended field ispresent in the FIC header through the FIC_chunk_header_extension_lengthvalue and thus skips a num_MH1.1_ensembles field. Accordingly, the CMMreceiver reads only the num_ensembles field and thus performs processingonly on a loop for MH1.0 ensemble in an FIC payload. In an embodiment,since the CMM receiver has skipped the num_MH1.1_ensembles field, a loopfor an MH1.1 ensemble is not a field expected by the CMM receiver andthus is processed as stuffing data. As a result, the CMM receiver skipsall SFCMM ensemble loops.

As shown in FIG. 25( b), when an SFCMM receiver parses an FIC headerhaving an extended field, the SFCMM receiver determines, through anFIC_chunk_minor_protocol_version value, that an extension for asignaling structure for an SFCMM is present in the FIC. The SFCMMreceiver then determines that an extended field is present in the FICheader through the FIC_chunk_header_extension_length value and thusreads a num_MH1.1_ensembles field. The SFCMM receiver processes an MH1.0ensemble loop indicated by num_ensembles and processes an MH1.1 ensembleloop indicated by num_MH1.1_ensembles.

FIG. 26 illustrates a method for processing a digital broadcast signalat the transmitting side according to an embodiment of the presentinvention.

The digital broadcast transmitting side generates signaling data formobile service signaling and performs RS encoding on the signaling data(S26010). Here, in an embodiment of the present invention, the generatedand RS-encoded signaling data is cross-layer information for connectionbetween the physical layer and the upper layers. The signaling data mayinclude information indicating the number of SFCMM ensembles. Thisinformation allows the receiving side to determine the number of SFCMMensembles and to process the same number of SFCMM ensemble loops as thenumber of SFCMM ensembles included in an FIC payload.

The signaling data may include information indicating whether or not anextension having a signaling data structure is present, informationindicating whether or not the extension having a signaling datastructure is backwards compatible, information indicating the length ofan added field in the extended signaling data structure, and the like.

The transmitting side creates data groups to be transmitted by insertingRS-encoded signaling data and mobile service data for providing a mobileservice into the data groups (S26030). Details of the data groups to betransmitted are similar to those described above with reference to FIGS.12 and 13.

The transmitting side converts the signaling data and the mobile servicedata included in the data groups into mobile service data packets(S26050). The mobile service data packets include data items used forthe mobile service in addition to the signaling data and the mobileservice data.

The transmitting side transmits a digital broadcast signal including thedata groups including the signaling data and the mobile service data(S26070).

The signaling data includes signaling information according to the SFCMMand the CMM. Here, the SFCMM is a mode in which more than 118 packetsamong 156 packets included in one slot are used to transmit mobileservice data and the CMM is a mode in which 118 or fewer packets among156 packets included in one slot are used to transmit mobile servicedata. In an embodiment of the present invention, packets that are notused for mobile service data among 156 packets included in one slot areused for main service data. That is, the number of main service datapackets included in one slot may vary according to whether the mode isSFCMM or CMM.

The SFCMM may flexibly transmit a larger number of mobile service datapackets than the CMM as needed. Accordingly, it is possible to achieve aflexible mobile service.

FIG. 27 illustrates a method for processing a digital broadcast signalat the receiving side according to an embodiment of the presentinvention.

The receiver receives a digital broadcast signal including data groupsincluding signaling data and mobile service data (S7010). Here, in anembodiment of the present invention, the signaling data is cross-layerinformation for connection between the physical layer and the upperlayers. The signaling data may include information indicating the numberof SFCMM ensembles. This information allows the receiving side todetermine the number of SFCMM ensembles and to process the same numberof SFCMM ensemble loops as the number of SFCMM ensembles included in anFIC payload.

The signaling data may include information indicating whether or not anextension having a signaling data structure is present, informationindicating whether or not the extension having a signaling datastructure is backwards compatible, information indicating the length ofan added field in the extended signaling data structure, and the like.

The receiver performs demodulation on the received digital broadcastsignal (S27030). For a more detailed description of this process, referto the above description of the baseband processor with reference toFIG. 23.

The receiver decodes signaling data included in the demodulated digitalbroadcast signal (S27050). This signaling data provides the receiverwith information regarding ensembles including a specific mobile serviceto allow the receiver to process specific mobile service data among themobile service data.

For details of information items included in the signaling data, referto the above description of FIGS. 19 and 20. The information itemsincluded in the signaling data are used in a procedure in which thereceiver identifies and decodes mobile service data associated with aspecific mobile service included in a digital broadcast signal in orderto provide the specific mobile service to the user.

As described above, the transmitting system, the receiving system, andthe method of processing broadcast signals according to the presentinvention have the following advantages.

When transmitting mobile service data through a channel, the presentinvention may be robust against errors and backward compatible with theconventional digital broadcast receiving system.

This invention extends a region for mobile service data in a slot. Thus,the transmitter can transmit more mobile service data.

This invention has an advantage enhancing the reception performance of abroadcast signal at a reception system, and a method for processing abroadcast signal by inserting additional known data in regions C, D andE.

The present invention is even more effective when applied to mobile andportable receivers, which are also liable to a frequent change inchannel and which require protection (or resistance) against intensenoise.

According to this invention, through extended FIC data, a receiver canappropriately process service data transmitted in the SFCMM and in theCMM. This invention provides a signaling method that allows SFCMM datato be processed through an extension of the FIC.

This invention also provides a method that allows a CMM receiver, whichcannot read SFCMM data, to receive and process an extended FIC. Thus,there is no need to generate and transmit respective FIC data for theSFCMM and the CMM and it is possible to use FIC data having the samestructure for signaling of SFCMM and CMM data.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

What is claimed:
 1. A method of processing a digital broadcasting signalin a transmitter, the method comprising, performing RS (Reed-Solomon)encoding on signaling data containing cross layer information between aphysical layer and a upper layer; interleaving the RS encoded signalingdata, wherein the interleaving the RS encoded signaling data comprises:writing the RS encoded signaling data row-by-row from left to right andtop-to-bottom in a signaling data block; and outputting the signalingdata in the signaling data block by reading column by column fromtop-to-bottom and left-to-right, wherein the signaling data includes afirst field indicating a protocol version change of the signaling data,a second field indicating a length of an extension field of a headerincluded in the signaling data, a first transmission ensemble numberfield indicating a number of ensembles for a first transmission mode,and a second transmission ensemble number field indicating a number ofensembles for a second transmission mode, and wherein the ensemblesinclude a collection of services, each of the services being a packageof packetized streams of mobile service data; transmitting the digitalbroadcasting signal including the mobile service data and theinterleaved signaling data during slots, wherein the first transmissionmode is a mode in which the mobile service data are transmitted whilereserving greater than 118 packets out of 156 packets in a slot and thesecond transmission mode is a mode in which the mobile service data aretransmitted while reserving less than or equal to 118 packets out of 156packets in the slot, wherein the second field is also used to skip thefirst transmission ensemble number field by a receiver for the secondtransmission mode.
 2. The method of claim 1, wherein the signaling datafurther includes the header and a payload, and wherein the first field,second field, first transmission ensemble number field and secondtransmission ensemble number field are included in the header.
 3. Themethod of claim 2, wherein the payload includes a first transmissionmode service number field indicating a number of services included in anensemble for the first transmission mode, and a second transmission modeservice number field indicating a number of services included in anensemble for the second transmission mode.
 4. The method of claim 3,wherein the second transmission ensemble number field and the secondtransmission mode service number field are used by the receiver for thesecond transmission mode to identify effective size of the signalingdata that is applicable to the receiver for the second transmissionmode.
 5. The method of claim 4, wherein the second transmission modeservice number field is treated as stuffing in the signaling data by thereceiver for the second transmission mode.
 6. A transmitter fortransmitting a digital broadcasting signal, the transmitter comprising:an encoder configured to perform RS (Reed-Solomon) encoding on signalingdata containing cross layer information between a physical layer and aupper layer; a signaling interleaver configured to interleave the RSencoded signaling data, wherein the signaling interleaver is furtherconfigured to: write the RS encoded signaling data row-by-row from leftto right and top-to-bottom in a signaling data block; and output thesignaling data in the signaling data block by reading column by columnfrom top-to-bottom and left-to-right, wherein the signaling dataincludes a first field indicating a protocol version change of thesignaling data, a second field indicating a length of an extension fieldof a header included in the signaling data, a first transmissionensemble number field indicating a number of ensembles for a firsttransmission mode, and a second transmission ensemble number fieldindicating a number of ensembles for a second transmission mode, andwherein the ensembles include a collection of services, each of theservices being a package of packetized streams of mobile service data; atransmission unit configured to transmit the digital broadcasting signalincluding the mobile service data and the interleaved signaling dataduring slots, wherein the first transmission mode is a mode in which themobile service data are transmitted while reserving greater than 118packets out of 156 packets in a slot and the second transmission mode isa mode in which the mobile service data are transmitted while reservingless than or equal to 118 packets out of 156 packets in the slot,wherein the second field is also used to skip the first transmissionensemble number field by a receiver for the second transmission mode. 7.The transmitter of claim 6, wherein the signaling data further includesthe header and a payload, and wherein the first field, second field,first transmission ensemble number field and second transmissionensemble number field are included in the header.
 8. The transmitter ofclaim 7, wherein the payload includes a first transmission mode servicenumber field indicating a number of services included in an ensemble forthe first transmission mode, and a second transmission mode servicenumber field indicating a number of services included in an ensemble forthe second transmission mode.
 9. The transmitter of claim 8, wherein thesecond transmission ensemble number field and the second transmissionmode service number field are used by the receiver for the secondtransmission mode to identify effective size of the signaling data thatis applicable to the receiver for the second transmission mode.
 10. Thetransmitter of claim 9, wherein the second transmission mode servicenumber field is treated as stuffing in the signaling data by thereceiver for the second transmission mode.